cancel
Showing results for 
Search instead for 
Did you mean: 

Further issues with 4.6D Export. Please help

Former Member
0 Kudos

Hi people,

We are currently trying to run an test export on 4.6D, and we've had a whole bunch of problems with the DB passwords and the SAP passwords connection to ORACLE,

but we've run a sql script that resets all these users and roles. This got us past the problems we were having, but we have now hit a problem that I can't find any solution

to. I'll paste the log generated below, but it's still an issue with the passwords, but we've edited the passwords to make sure they're standard in SQL.

The users we have done are

SAPR3

SYS

SYSTEM

Are there any others we should look at? Can you think of anything else we can try???

The export fails in the GUI at 55%, when it's trying to do this...

"The tool R3szchk creates files that contain size information on the database (*.EXT files and the file DBSIZE<DB>.TPL). This step starts R3szchk."

The error we get in the log is as follows.

Thanks...

INFO 2007-10-30 11:59:56 DBEXPORTINSTANCE_IND_ORA InternalWarmKeyCheck:0

The installation phase is starting now. Please look in the log

file for further information about current actions.

INFO 2007-10-30 11:59:56

Requesting Export Details

INFO 2007-10-30 11:59:56

Requesting Export Details

INFO 2007-10-30 11:59:56 CHKLIBPATH_IND_ORA InternalWarmKeyCheck:0

No shared library search path needed for database ORA!

INFO 2007-10-30 11:59:56

Checking the Library Path

INFO 2007-10-30 11:59:56

Requesting Export-Specific Parameters

INFO 2007-10-30 11:59:56

Testing the Database Connect

INFO 2007-10-30 11:59:56

Testing the Database Connect

INFO 2007-10-30 11:59:56 DBEXPSERVER_IND_IND InternalWarmKeyCheck:0

The CD CDEXPORT1 will not be copied.

INFO 2007-10-30 11:59:56

Requesting Information on CD-ROMs

INFO 2007-10-30 11:59:56

Creating the Export Directories

INFO 2007-10-30 11:59:56

Updating the Database Statistics for the Export

INFO 2007-10-30 11:59:56

Updating the Database Statistics

INFO 2007-10-30 11:59:56

Creating the R3load Control Files

INFO 2007-10-30 11:59:56

Creating the Size Information Files

INFO 2007-10-30 11:59:56 R3SZCHK_IND_ORA R3ldctlDo:0

/sapmnt/QTG/exe/R3szchk -s DD -g ora 8 -p /software/inst_temp -f

/software/inst_temp/SAPSDIC.STR /software/inst_temp/SAPUSER.STR

/software/inst_temp/SAPAPPL1.STR /software/inst_temp/SAPAPPL2.STR

/software/inst_temp/SAPAPPL0.STR /software/inst_temp/SAPSDOCU.STR

/software/inst_temp/SAPSSRC.STR /software/inst_temp/SAPSPROT.STR

/software/inst_temp/SAPCLUST.STR /software/inst_temp/SAPPOOL.STR

/software/inst_temp/SAPSSEXC.STR /software/inst_temp/SAP0000.STR

/software/inst_temp/SAPSSDEF.STR /software/inst_temp/SAPSLDEF.STR

/software/inst_temp/SAPSLEXC.STR /software/inst_temp/SAPSLOAD.STR

/software/inst_temp/SAPUSER1.STR

INFO 2007-10-30 11:59:56 R3SZCHK_IND_ORA SyCoprocessCreate:300

Creating coprocess /sapmnt/QTG/exe/R3szchk -s DD -g ora 8 -p

/software/inst_temp -f /software/inst_temp/SAPSDIC.STR

/software/inst_temp/SAPUSER.STR /software/inst_temp/SAPAPPL1.STR

/software/inst_temp/SAPAPPL2.STR /software/inst_temp/SAPAPPL0.STR

/software/inst_temp/SAPSDOCU.STR /software/inst_temp/SAPSSRC.STR

/software/inst_temp/SAPSPROT.STR /software/inst_temp/SAPCLUST.STR

/software/inst_temp/SAPPOOL.STR /software/inst_temp/SAPSSEXC.STR

/software/inst_temp/SAP0000.STR /software/inst_temp/SAPSSDEF.STR

/software/inst_temp/SAPSLDEF.STR /software/inst_temp/SAPSLEXC.STR

/software/inst_temp/SAPSLOAD.STR /software/inst_temp/SAPUSER1.STR

...

INFO 2007-10-30 11:59:57 R3SZCHK_IND_ORA R3ldctlDo:0

DbSl Trace: OCI-call 'olog' failed: rc = 1017

DbSl Trace: CONNECT failed with sql error '1017'

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hello,

If you changed the SAPR3 pwd, you must change it at OPS$ users table. Something like:

SQL> <i>insert into OPS$QTGADM.SAPUSER values ('SAPR3','<<b>your_new_pwd</b>>');</i>

After commit, test it with R3trans -d (qtgadm user).

Best Regards,

JC Llanes.

former_member204746
Active Contributor
0 Kudos

check OPS$ authentication.

SAP Note 400241 - problem with OPS$

Former Member
0 Kudos

Hi Bradley,

It seems a problem with the OPS$ user. Sap Note 400241 will help you to solve it.

Best Regards,

JC Llanes.

Former Member
0 Kudos

I've looked at the note, and done the things it has advised. Still no joy.

Thanks for the reply tho...