cancel
Showing results for 
Search instead for 
Did you mean: 

Terminating with error code 12 on startsap

Former Member
0 Kudos

Hi all,

Can anybody help me pls? Below is my problem.

I installled a fresh instance (call it UAT) of SAP ECC6 on my server. The, I restored an offline backup of my PROD instance to this UAT instance. When I tried to start using startsap, I had the error:

saposcol already running

Running /usr/sap/UAT/SYS/exe/run/startdb

Trying to start UAT database ...

Log file: /home/uatadm/startdb.log

/usr/sap/UAT/SYS/exe/run/startdb: Terminating with error code 12

DB startup failed

Im using ECC6.0 using Oracle Database 10.2.0.2 on an IBM AIX 5.3 machine. I am able to start the database manually but I cant do it in startsap.

Below are some of the errors in trans.log when issuing R3trans -d

4 ETW000 [dboci.c ,00000] *** ERROR => OCI-call 'OCISessionBegin' failed:

rc = 1017

4 ETW000

1295 0.040616

4 ETW000 [dbsloci. ,00000] *** ERROR => CONNECT failed with sql error '1017

'

4 ETW000

25 0.040641

4 ETW000 [dblink ,00431] ***LOG BY2=>sql error 1017 performing CON [dbl

ink#3 @ 431]

4 ETW000

81 0.040722

4 ETW000 [dblink ,00431] ***LOG BY0=>ORA-01017: invalid username/password

; logon denied [dblink#3 @ 431]

4 ETW000

28 0.040750

2EETW169 no connect possible: "DBMS = ORACLE --- dbs_o

ra_tnsname = 'UAT'"

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Thank you for the response. The problem is now solved

former_member204746
Active Contributor
0 Kudos

do not close post like this, provide feedback and tell us how problem was fixed.

Former Member
0 Kudos

Opps, sorry Eric. My problem was solved by Rajesh's recommendation. That is to set

login/no_automatic_user_sapstar = 0

then delete the SAP* account from the backend using the provided script. I restarted the instance and it solved the problem

Former Member
0 Kudos

This message was moderated.

Former Member
0 Kudos

Hi,

LOG BY0=>ORA-01017: invalid username/password

If your SID of new instance is different that OLD instance, then you will need to create or change the OPS$ users.

Also you need to change the password of your schema user.

    1. To create OPS$ user:

#su - orauat
sqlplus / as sysdba
SQL> create user OPS$UATADM default tablespace PSAPSR3USR temporary tablespace PSAPTEMP identified externally;
SQL> grant connect, resource to OPS$UATADM;
    1. To change the schema users password: (as ora<sid> user)

# brconnect -u system/<syst_pwd> -f chpass -o SAPR3 -p <new_sap_pwd>

Please go through the below note. and link of other similar thread for detail steps.

[|]

[50088 - Creating OPS$ users on Windows NT-Oracle.pdf|https://service.sap.com/sap/support/notes/50088]

[361641 - Creating OPS$ users on UNIX.pdf|https://service.sap.com/sap/support/notes/361641]

[400241 - Problems with ops$ or sapr3 connect to Oracle.pdf|https://service.sap.com/sap/support/notes/400241]

Regards

Rajesh Narkhede

Former Member
0 Kudos

Hi,

Thanks for the response.

Im trying to execute the first step but I get an ORA-01031 error. See below:

  1. su - orauat

AMC-ERP-UAT:orauat 1> sqlplus /nolog

SQL*Plus: Release 10.2.0.2.0 - Production on Wed May 12 16:21:36 2010

Copyright (c) 1982, 2005, Oracle. All Rights Reserved.

SQL> connect / as sysdba

ERROR:

ORA-01031: insufficient privileges

SQL>

Is it ok if I use 'connect sys/<password> as sysdba instead of 'connect / as sysdba'?

Former Member
0 Kudos

Hi,

Is it ok if I use 'connect sys/<password> as sysdba instead of 'connect / as sysdba'?

Yes, its ok if you can login as "sysdba". If the above command won't work. try below one...

SQL> connect sys/<password>@SID as sysdba

Regards.

Rajesh Narkhede

Former Member
0 Kudos

Hi Rajesh,

Please see error below during brconnect. SAPR3 is not a valid owner. How do I determine the name of the owner to use?

Thanks

  1. su - orauat

AMC-ERP-UAT:orauat 1> brconnect -u system/e6padm1n -f chpass -o SAPR3 -p uatadm1

n

BR0801I BRCONNECT 7.00 (18)

BR0824E Owner 'SAPR3' not found in database or not SAP owner

BR0182E Checking parameter/option 'chpass_owner/-o' failed

BR0280I BRCONNECT time stamp: 2010-05-12 16.49.44

BR0804I BRCONNECT terminated with errors

AMC-ERP-UAT:orauat 2> set -o vi

set: Syntax error.

AMC-ERP-UAT:orauat 3>

ashish_mishra2
Contributor
0 Kudos

>

> Please see error below during brconnect. SAPR3 is not a valid owner. How do I determine the name of the owner to use?

>

> BR0801I BRCONNECT 7.00 (18)

> BR0824E Owner 'SAPR3' not found in database or not SAP owner

Hi,

1.: From sidadm check the value of env variable dbs_ora_schema, is this SAPR3 or SAPSR3 or something else ?

<sidadm:> env | grep -i dbs_ora_schema

2: execute R3trans -d and read the detailed logs of trans.log . check the user what it is using for connecting to database.

e.g Connecting as SAPSR3/<pwd>@<sid> on connection 0 (nls_hdl 0) ... (dbsl 700 250407)

If the user being used in above both the points is not same, set the environment variable from sidadm

setenv dbs_ora_schema SAP<xxx>

Cheers !!!

Ashish

Former Member
0 Kudos

Hi,

BR0824E Owner 'SAPR3' not found in database or not SAP owner

You can check the schema owner in SOURCE system as below:

1. by using below command as <sid>adm.

# echo $dbs_ora_schema

Use the same schema owner in below command on TARGET system.

For example:

# brconnect -u system/e6padm1n -f chpass -o <schema_owner> -p uatadm1

Also make sure that environment variable "dbs_ora_schema" is set properly for <sid>adm and ora<sid> user in TARGET system.

Regards.

Rajesh Narkhede

Former Member
0 Kudos

Hi,

Hi, I have run the command successfully. Just a question though. Im expecting the last line to be OPS$UATADM.SAPUSER instead of OPS$E6PADM.SAPUSER because the new SID is UAT. Is this ok?

AMC-ERP-UAT:orauat 8> brconnect -u sys/uatadm1n -f chpass -o SAPSR3 -p uatadm1n

BR0801I BRCONNECT 7.00 (18)

BR0280I BRCONNECT time stamp: 2010-05-12 18.30.15

BR0828I Changing password for database user SAPSR3

BR0280I BRCONNECT time stamp: 2010-05-12 18.30.15

BR0256I Enter 'c[ont]' to continue, 's[top]' to cancel BRCONNECT:

c

BR0280I BRCONNECT time stamp: 2010-05-12 18.30.16

BR0257I Your reply: 'c'

BR0259I Program execution will be continued...

BR0280I BRCONNECT time stamp: 2010-05-12 18.30.16

BR0829I Password changed successfully in database for user SAPSR3

BR0830I Password changed successfully in table OPS$E6PADM.SAPUSER for user SAPSR3

Former Member
0 Kudos

Hi,

No. It should be OPS$UATADM.SAPUSER instead of OPS$E6PADM.SAPUSER

Better you check the things step by step as below and correct as needed.

  1. To see the current DBA users. You may find old <SID>adm user in the query result.

SQL> SELECT USERNAME,PASSWORD FROM DBA_USERS;

  1. If you find old <SID>adm user, drop it using the below command.

SQL> DROP USER OPS$<SID>ADM CASCADE;

SQL> COMMIT;

  1. Then create new OPS$ user as per current <SID>adm user and assign default tablespaces. Grant privileges to the newly created user.

SQL> CREATE USER OPS$<SID>ADM IDENTIFIED BY <NEW_PASSWORD>

TEMPORARY TABLESPACE PSAPTEMP

PROFILE DEFAULT;

SQL> GRANT CONNECT, RESOURCE TO OPS$<SID>ADM;

  1. Check if OPS$<SID>ADM.SAPUSER table is exist. You can also drop this table as below.

SQL> DROP TABLE OPS$<SID>ADM.SAPUSER;

SQL> COMMIT;

  1. Recreate the above table manually.

SQL> CREATE TABLE OPS$<SID>ADM.SAPUSER

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

  1. Insert the SAPSR3 user and password in above table.

SQL> INSERT INTO OPS$<SID>ADM.SAPUSER VALUES ('SAPR3', 'NEW_PASSWORD');

  1. Change the SAPSR3 users password.

SQL> ALTER USER SAPR3 IDENTIFIED BY <NEW_PASSWORD>;

  1. Check if the above table is properly created and has the entry for SAPSR3 user.

SQL> SELECT USERID,PASSWD FROM SAPUSER;

  1. If you changed the SID during system copy, it is recommended to adapt the global_name parameter with the below SQL command.

SQL> ALTER DATABASE RENAME GLOBAL_NAME TO <TSID>;

Regards.

Rajesh Narkhede

ashish_mishra2
Contributor
0 Kudos

Hi,

you can drop the source system OPS$ user using brtools and create the same for source system if not existing.

from sqlplus '/as sysdba'

select username from dba_users;

drop user ops$<source SID>ADM cascade;

select * from dba_role_privs where grantee like 'OPS%';

grant connect,resource to OPS$<target SID>ADM with admin option;

Cheers !!!

Ashish

Former Member
0 Kudos

Hi,

Thank you very much for all the support provided. Im now able to run startsap successfully. I have one last question however, I tried logging in to the new instance (UAT) instance but Im having the problem below:

Logon no possible (error in license check).

Im trying to login using SAP* so that I can enter the proper license key but Im not allowed to login. I got an invalid password message. Is there a way to reset the SAP* account?

Thanks

Former Member
0 Kudos

Hi,

Set the below profile parameter in INSTANCE or DEFAULT profile.

login/no_automatic_user_sapstar = 0

Then restart the SAP system. It will activate emergency SAP* user which is hard coded in SAP Kernel.

and login with "SAP*" and "pass".

Install the correct license..

If you still failed to login with "invalid password message" then you need to delete SAP* user from USR02 table with below SQL command.

SQL> DELETE FROM SAPSR3.USR02 WHERE BNAME = 'SAP*' AND MANDT = '000';

SQL> COMMIT;

Then try again to login into CLIENT 000 with user "SAP*" and password "pass"

Regards.

Rajesh Narkhede