DB13 problems after system copy

[Former Member]

Dear support,

I have done system copy and followed post installation steps but i am not able to execute any job through DB13 even after setting ops$ mechanism.

i get below job logs for any action started from DB13

Job started

Step 001 started (program RSDBAJOB, variant &0000000000002, user name SAP*)

Execute log. command SAPDBA on host cssl-020

__Parameters: -u / -checkopt PSAP% -method E

External program terminated with exit code 128

SAPDBA returned error status E

Job finished

changes i made:

I have deleted all ops$PRD users and created new ones as below for DEV

DROP USER OPS$PRDADM CASCADE;

create user OPS$DEVADM default tablespace psapuser1d

temporary tablespace psaptemp identified externally;

GRANT CONNECT, RESOURCE TO "OPS$DEVADM";

DROP TABLE "OPS$PRDADM".SAPUSER;

CREATE TABLE "OPS$DEVADM".SAPUSER

(USERID VARCHAR2(256), PASSWD VARCHAR2(256));

INSERT INTO "OPS$DEVADM".SAPUSER VALUES ('SAPR3','sap');

alter user SAPR3 identified by sap;

what else i should perform after this to get through , i have folllowed these steps from sap standard note.

<b>Please let me know procedure in detail.</b>

Best Regards,

AjitR

[Former Member]

Hi Ajit,

I beleive you made a copy form PRD to DEV system.

Seems you missed out on creating OPS$ORADEV user.Execute the below steps again.

sqlplus "/ as sysdba"

shutdown

startup open

drop table ops$prdadm.sapuser;

drop table ops$prdadm.cascade;

drop table ops$oraprd.sapuser;

drop table ops$oraprd.cascade;

Now Setup OPS$CONNECT for ORADEV(with default password for sapr3)

CREATE USER OPS$ORADEV IDENTIFIED EXTERNALLY DEFAULT TABLESPACE PSAPUSER1D TEMPORARY TABLESPACE PSAPTEMP;

GRANT CONNECT,RESOURCE,DBA TO OPS$ORADEV WITH ADMIN OPTION;

CREATE TABLE "OPS$DEVADM".SAPUSER (USERID VARCHAR2(256),PASSWD VARCHAR2(256):

INSERT INTO "OPS$DEVADM".SAPUSER VALUES ( 'sapr3', 'sap');

<b>Now Setup OPS$CONNECT for DEVADM</b>

CREATE USER OPS$DEVADM IDENTIFIED EXTERNALLY DEFAULT TABLESPACE PSAPUSER1D TEMPORARY TABLESPACE PSAPTEMP;

GRANT CONNECT,RESOURCE,DBA TO OPS$DEVADM WITH ADMIN OPTION;

COMMIT WORK;

EXIT

<b>Change the password of szstem/sapr3 to default</b>

brconnect -u / -p initDEV.sap -1 D -f chpass -o system -p manager

continue(press c)

brconnect -u / -p initDEV.sap -1 D -f chpass -o sapr3 -p manager

you need to initialise ops$ for sap connection

also start the DB in archive log mode and later remove the obsolete redo logs from oraarch .Check if your listener is up and running

**Reward points accrodingly

Junaid

[former_member618758]

Hi,

You might have a newer BRCONNECT Version 6.XX.

The -checkopt is replaced by new BRCONNECT functions like brconnect -f stats.

So in summary I recommand you to:

Run the following scripts (location of download is outlined in note

403704)

db13brc.sql : this updates the SDBAC table so that the brconnect

jobs are scheduled from DB13 and not sapdba.

dbstatc.sql: this updates the DBSTATC table so it has the

default values for connection.

dbcheckora.sql: this updates the check conditions in DB17.

The latest brtools version can be downloaded using the following note

12741.

This should help,

George

[Former Member]

Is these BRtools are compatible to sap 4.0B_ext with Oracle 8.1.7.4 because that is my uerrent version.

Best Regards,

AjitR.

[Former Member]

BRtools utility is applicable form SAP WAS 6.20 and not to any 4.X releases of sap.

[Former Member]

Then how to go ahead with my problem

[Former Member]

Hi Ajit,

With 4.x versions, you must run the <b>chdbpass</b> script (is located at <b>$ORACLE_HOME/dbs/</b>). Run it with the <b>orasid </b>user, and proceed to create the OPS$ and initialize the SAPR3 user password.

Best Regards,

JC Llanes.

[Former Member]

> BRtools utility is applicable form SAP WAS 6.20 and

> not to any 4.X releases of sap.

Sorry, but this is not correct.

BRTOOLS ( the binary ) can only be used at OS and it does not depend on the BASIS release.

BR* tools ( brbackup, brconnect, brarchive ... ) can ( and should ) be used with 4.x releases.

Limitation is the Database version, BR* tools version 700 only works with Oracle 10g and 9i. BR* tools version 6.40 does not work with Oracle 8.x

Regarding the initial issue.

Not really sure if all advice here is usefull.

Can you execute the mentioned command at OS level?

Have you check the log for other errors?

Have you check the BR* authorizations?

[Former Member]

>>BR* tools version 700 only works with Oracle 10g and 9i.

that's valid vor unix.

on Windows

BR* tools version 700 only works with Oracle 10g

BR* tools version 640 only works with Oracle 9i.

Peter

[Former Member]

True, I keep forgetting about Windows, sorry <img src="http://img117.exs.cx/img117/6721/o4fsad.gif" alt="Sad" />