BW 3.5 Homogeneous System Copy 32bit to 64bit

[Former Member]

Hi Experts,

I am trying to migrate an existing BW 3.5 system on 32bit to 64bit machine via the ABAP content DB export. OS from Win2000 32bit to Win2003 64bit. Ora DB from 9.2.0.8 to 10.2.0.2

I got the following error in the R3ldctlExport.log file

DbSl Trace: ORA-1403 when accessing table SAPUSER

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

DbSl Trace: CONNECT failed with sql error '1017'

ERROR: DbSlConnect rc= 99

DbSl Trace: ORA-1403 when accessing table SAPUSER

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

DbSl Trace: CONNECT failed with sql error '1017'

When i checked the source DB the table SAPUSER is in a tablespace called PSAPUSER1D & the owner of the table is user OPS$CB.

Is there any way to proceed or to trick the SAPinst program to read the table SAPUSER above?

I believe this problem is due to the source DB has a non SAP standard tablespace naming convention. it should be PSAP<SID>USR.

Regards,

Amal

[andreas_herzog · Accepted solution]

you are using a wrong login (either user and/or password is wrong)

-> did you try to connect as user SYS? (eg. connect sys/<pwd>@<SID> )

GreetZ, AH

[Former Member]

Hi,

i just checked SP note 400241 & apply the General checks n corrections mentioned. problem is due to the public synonym. drop the synonym & recreate back. Later rerun the export & it worked ok

[Former Member]

OPS$CB is not a valid OPS$ user on sap/windows:

CB is not a valid SID (has to have 3 characters).

depending wether you are using Domain or Computer local users your valid OPS$ username would be: OPS$<domainname|computername><SID>.

see note 50088 for more information.

regards

Peter