Severe error(s) occured in phase MAIN_SHDINST/SUBMOD_SHDALIASCRE/SCEXEC_ALIAS!

[Former Member]

Dear Gurus,

While upgrading Solution Manager from 7.0 EHP1 to 7.1 SR1, under PRE-PROCESSING stage, I am getting following error message under SCEXEC_ALIAS phase:-

Severe error(s) occured in phase MAIN_SHDINST/SUBMOD_SHDALIASCRE/SCEXEC_ALIAS!

Last error code set: 9 processes failed, check 'SCEXEC_A.*' for details

Please find the following log details in SCEXEC_A* log files:-

BLOCKED SIGNALS: ''

SAPup> Starting subprocess 6881376 at 20121123153110

ENV: DIR_LIBRARY=/usr/sap/SOL/SOLMANUP/abap/exenew

ENV: JAVA_HOME=/usr/java14_64

ENV: LIBPATH=/usr/sap/SOL/SOLMANUP/abap/exenew:/usr/sap/SOL/SOLMANUP/jvm/jre/lib/ppc64/server:/usr/sap/SOL/SOLMANUP/jvm/jre/lib/ppc64:/usr/sap/SOL/SOLMANUP/jvm/jre/../lib/ppc64:/usr/sap/SOL/SOLMANUP/jvm/jre/lib/ppc64/jli:/usr/sap/SOL/SOLMANUP/jvm/jre/../lib/ppc64/jli:/usr/lib:/lib:/usr/sap/SOL/SYS/exe/run:/oracle/client/10x_64/instantclient

ENV: NLS_LANG=AMERICAN_AMERICA.UTF8

ENV: ORACLE_BASE=/oracle

ENV: ORACLE_HOME=/oracle/SOL/11203

ENV: ORACLE_SID=SOL

ENV: PATH=/usr/sap/SOL/SOLMANUP/abap/exenew:/oracle/SOL/11203/bin:.:/home/soladm:/usr/sap/SOL/SYS/exe/run:/usr/bin:/etc:/usr/sbin:/usr/ucb:/usr/dt/bin:/usr/bin/X11:/sbin:/usr/java14_64/jre/bin:/usr/java14_64/bin

ENV: SAPSYSTEMNAME=SOL

ENV: auth_shadow_upgrade=1

ENV: dbms_type=ORA

ENV: dbs_ora_schema=SAPSR3

ENV: dbs_ora_tnsname=SOL

EXECUTING /usr/sap/SOL/SOLMANUP/abap/exenew/tp (/usr/sap/SOL/SOLMANUP/abap/exenew/tp) pf=/usr/sap/SOL/SOLMANUP/abap/bin/EXDBNEW.TPP execdbscript SOL -x PTALDC02.XQL DBEXECNONT DBEXECNOCHECK

This is /usr/sap/SOL/SOLMANUP/abap/exenew/tp version 380.03.82 (release 720, unicode enabled)

ERROR: Connect to SOL failed (20121123153110, probably wrong environment).

Warning: Parameter INTERRUPT is no longer used.

Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.

Warning: Parameter WITH_TACOB is no longer used.

Warning: Parameter IMPDP_BY_EVENT is no longer used.

Warning: Parameter INTERRUPT is no longer used.

Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.

Warning: Parameter WITH_TACOB is no longer used.

Warning: Parameter IMPDP_BY_EVENT is no longer used.

Warning: Parameter DBCONFPATH is no longer used.

TRACE-INFO: 1:  [     dev trc,00000]  Fri Nov 23 15:31:10 2012                                                         9868  0.009868

TRACE-INFO: 2:  [     dev trc,00000]  DlLoadLib() success: dlopen("/usr/sap/SOL/SOLMANUP/abap/exenew/dboraslib.o"), hdl 0

TRACE-INFO: 3:                                                                                                           29  0.009897

TRACE-INFO: 4:  [     dev trc,00000]  -->DbSlConnect(vers=0, type=0, env='[default env]', userid='SAPSR3')            13313  0.023210

TRACE-INFO: 5:  [     dev trc,00000]  Register application info.                                                        621  0.023831

TRACE-INFO: 6:  [     dev trc,00000]  Oracle client version: 10.2.0.4.0, V3, (dbsl 720 251111, UNICODE[2])               98  0.023929

TRACE-INFO: 7:  [     dev trc,00000]  Installed Oracle client patches:                

.

.

.

.

TRACE-INFO: 14:  [     dev trc,00000]  # Patch  6775231      : Created on  1 Dec 2008, 03:36:38 hrs PST8PDT               30  0.015144
TRACE-INFO: 15:  [     dev trc,00000]    Default connection: tnsname ='SOL'                                               20  0.015164
TRACE-INFO: 16:  [     dev trc,00000]  -->oci_initialize(con=0, char='UTF16', nchar='AL16UTF16', nls=-1),uc_ln=2          22  0.015186
TRACE-INFO: 17:  [     dev trc,00000]  OCIEnvCreate(mode=16384=OCI_UTF16) returned 0 (for default NLS handle)       3575  0.018761
TRACE-INFO: 18:  [     dev trc,00000]     OCIHandleAlloc(OCI_HTYPE_ERROR, con=0, ErrHp=11225a108)                         35  0.018796
TRACE-INFO: 19:  [     dev trc,00000]     OCIHandleAlloc(OCI_HTYPE_ERROR, con=0, ErrBt=1122599b8)                         20  0.018816
TRACE-INFO: 20:  [     dev trc,00000]  NLS env. settings: lang=0041004D00450052004900430041004E                          106  0.018922
TRACE-INFO: 21:  [     dev trc,00000]                     terr=0041004D00450052004900430041                               28  0.018950
TRACE-INFO: 22:  [     dev trc,00000]                     char=00550054004600310036                                       30  0.018980
TRACE-INFO: 23:  [     dev trc,00000]  Client NLS setting (by OCINlsGetInfo(con=0)): 'AMERICAN_AMERICA.UTF16'             20  0.019000
TRACE-INFO: 24:  [     dev trc,00000]  charset='UTF16', ncharset='AL16UTF16', UNI_ASC=FALSE                               18  0.019018
TRACE-INFO: 25:  [     dev trc,00000]  Connecting as SAPSR3SHD/<pwd>@SOL on connection 0 (nls 0) ... (dbsl 720 251111, UNICODE[2])
TRACE-INFO: 26:                                                                                                           28  0.019046
TRACE-INFO: 27:  [     dev trc,00000]     OCIHandleAlloc(OCI_HTYPE_SVCCTX, con=0, svchp=11225d788)                        29  0.019075
TRACE-INFO: 28:  [     dev trc,00000]  Allocating server context handle                                                   18  0.019093
TRACE-INFO: 29:  [     dev trc,00000]  Attaching to database server SOL (con=0, svchp=11225d788, srvhp=11225ecc8)         62  0.019155
TRACE-INFO: 30:  [     dev trc,00000]  Assigning server context 11225ecc8 to service context 11225d788                 66256  0.085411
TRACE-INFO: 31:  [     dev trc,00000]     OCIHandleAlloc(OCI_HTYPE_SESSION, con=0, usrhp=1122dfe50)                       48  0.085459
TRACE-INFO: 32:  [     dev trc,00000]  Assigning username to user session: con=0, usrhp= 1122dfe50                        20  0.085479
TRACE-INFO: 33:  [     dev trc,00000]  Assigning password to user session: con=0, usrhp=1122dfe50                         26  0.085505
TRACE-INFO: 34:  [     dev trc,00000]  Starting user session: OCISessionBegin(con=0, usr='SAPSR3SHD', svc=11225d788, srv=11225ecc8, usr=1122dfe50)
TRACE-INFO: 35:                                                                                                          167  0.085672
TRACE-INFO: 36:  [     dev trc,00000]  Sat Nov 24 12:37:39 2012                                                      10834921  10.920593
TRACE-INFO: 37:  [     dev trc,00000]     OCISessionBegin(OCI_DEFAULT) failed with -1=OCI_ERROR                           14  10.920607
TRACE-INFO: 38:  [     dev trc,00000]     OCISessionBegin(OCI_DEFAULT) failed with SQL error 1017:                        92  10.920699
TRACE-INFO: 39:  [     dev trc,00000]     ORA-01017: invalid username/password; logon denied                                                                       
TRACE-INFO: 40:                                                                                                           26  10.920725
TRACE-INFO: 41:  [    dbsloci.,00000]  *** ERROR => CONNECT failed with sql error '1017'                                  27  10.920752
TRACE-INFO: 42:  [     dev trc,00000]     set_ocica() -> SQL error code 1017                                              19  10.920771
TRACE-INFO: 43:  [     dev trc,00000]  -->oci_get_errmsg (con=0, rc=1017)                                                 20  10.920791
TRACE-INFO: 44:  [     dev trc,00000]     OCIErrorGet -> SQL error code: 1017                                             49  10.920840
TRACE-INFO: 45:  [     dev trc,00000]     ORA-01017: invalid username/password; logon denied                                                                       
TRACE-INFO: 46:                                                                                                           24  10.920864
TRACE-INFO: 47:  [     dev trc,00000]     DbSlConnect(con=0) -> orc=0, 99=DBSL_ERR_DB                                     23  10.920887
TRACE-INFO: 48:  [    dblink  ,00000]  ***LOG BY2=>sql error 1017   performing CON                                        53  10.920940
TRACE-INFO: 49:  [    dblink  ,00000]  ***LOG BY0=>ORA-01017: invalid username/password; logon denied                     28  10.920968

tp returncode summary:

TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0232
tp finished with return code: 232
meaning:
  connect failed

Then as per logs, I re-tried to execute the phase after executing following command:

alter user SAPSR3SHD account unlock;

alter user SAPSR3SHD identified by SAP;

Still , not succeeded.

Please help.

Regards,

Nilutpal

+91 9766897144

TRACE-INFO: 25:  [     dev trc,00000]  Connecting as SAPSR3SHD/<pwd>@SOL on connection 0 (nls 0) ... (dbsl 720 251111, UNICODE[2])
TRACE-INFO: 26:                                                                                                           46  0.030755
TRACE-INFO: 27:  [     dev trc,00000]     OCIHandleAlloc(OCI_HTYPE_SVCCTX, con=0, svchp=11225d788)                        49  0.030804
TRACE-INFO: 28:  [     dev trc,00000]  Allocating server context handle                                                   27  0.030831
TRACE-INFO: 29:  [     dev trc,00000]  Attaching to database server SOL (con=0, svchp=11225d788, srvhp=11225ecc8)        111  0.030942
TRACE-INFO: 30:  [     dev trc,00000]  Assigning server context 11225ecc8 to service context 11225d788                120782  0.151724
TRACE-INFO: 31:  [     dev trc,00000]     OCIHandleAlloc(OCI_HTYPE_SESSION, con=0, usrhp=1122dfe50)                       71  0.151795
TRACE-INFO: 32:  [     dev trc,00000]  Assigning username to user session: con=0, usrhp= 1122dfe50                        30  0.151825
TRACE-INFO: 33:  [     dev trc,00000]  Assigning password to user session: con=0, usrhp=1122dfe50                         40  0.151865
TRACE-INFO: 34:  [     dev trc,00000]  Starting user session: OCISessionBegin(con=0, usr='SAPSR3SHD', svc=11225d788, srv=11225ecc8, usr=1122dfe50)
TRACE-INFO: 35:                                                                                                          370  0.152235
TRACE-INFO: 36:  [     dev trc,00000]     OCISessionBegin(OCI_DEFAULT) failed with -1=OCI_ERROR                        11311  0.163546
TRACE-INFO: 37:  [     dev trc,00000]     OCISessionBegin(OCI_DEFAULT) failed with SQL error 1017:                        85  0.163631
TRACE-INFO: 38:  [     dev trc,00000]     ORA-01017: invalid username/password; logon denied                                                                       
TRACE-INFO: 39:                                                                                                           25  0.163656
TRACE-INFO: 40:  [    dbsloci.,00000]  *** ERROR => CONNECT failed with sql error '1017'                                  26  0.163682
TRACE-INFO: 41:  [     dev trc,00000]     set_ocica() -> SQL error code 1017                                              18  0.163700
TRACE-INFO: 42:  [     dev trc,00000]  -->oci_get_errmsg (con=0, rc=1017)                                                 19  0.163719
TRACE-INFO: 43:  [     dev trc,00000]     OCIErrorGet -> SQL error code: 1017                                             45  0.163764
TRACE-INFO: 44:  [     dev trc,00000]     ORA-01017: invalid username/password; logon denied                                                                       
TRACE-INFO: 45:                                                                                                           23  0.163787
TRACE-INFO: 46:  [     dev trc,00000]     DbSlConnect(con=0) -> orc=0, 99=DBSL_ERR_DB                                     22  0.163809
TRACE-INFO: 47:  [    dblink  ,00000]  ***LOG BY2=>sql error 1017   performing CON                                        72  0.163881
TRACE-INFO: 48:  [    dblink  ,00000]  ***LOG BY0=>ORA-01017: invalid username/password; logon denied                     28  0.163909tp returncode summary:TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0232
tp finished with return code: 232
meaning:
  connect failed
BLOCKED SIGNALS: ''
SAPup> Starting subprocess 3670036 at 20121123161810

[premsukh_bishnoi · Accepted solution]

Hi,

There is a problem with the OPS$ Login under your user.

Please check note 400241, to solve the issue.

Or

It seems that the user SAPSR3SHD cannot connect to DB. Has this user
the default password set or was this password changed?

Make sure you unlock properly SAPSR3SHD as per note 951167.

If required, try this command:
SQL> alter user SAPSR3SHD identified by <pass>;
SQL> select * from OPS$<SID>ADM.SAPUSER;
SQL> insert into OPS$<SID>ADM.SAPUSER
SQL> insert into "OPS$<SID>ADM".SAPUSER values ('SAPSR3SHD','<pass>');
SQL> commit;

Regards, Premsukh

[former_member185239 · Accepted solution]

First unlock the user :

alter user SAPSR3SHD account unlock;

alter user SAPSR3SHD identified by SAP;

password which you changed above is stored in dba_users table of your database.

Also keep the same password SAP in

Select owner from DBA_TABLES where TABLE_NAME="SAPUSER"

owner will be OPS$<SID>ADM

steps to follow :

1. select * from "OPS$<SID>ADM".SAPUSER.

2. check whether the password is same as SAP.

3. if not then run the sql query

   insert into "OPS$<SID>ADM".SAPUSER values('SAPSR3SHD','SAP');

Password in dba_users table and SAPUSER table must be the same.

Also follow the sapnote : 400241 , if you read it carefully you will find that they are using password sap in lowercase. If it does not work with password sap you can give a try with password 'pass' too.

With Regards

Ashutosh Chaturvedi

[Former Member · Accepted solution]

Dear Premsukh and Asutosh,

Thanks a lot for your help.

I have followed the steps mentioned by you.

Even I have maintained following parameters in init.ora file:-

REMOTE_OS_AUTHENT = TRUE
os_authent_prefix = ops$

Still, i didn't get succeeded. Please help.

Regards,

NIlutpal.

[former_member185239 · Accepted solution]

Hi Nilutpal,

Please change the parameter REMOTE_OS_AUTHENT = TRUE in SP file not in init.ora file.

Refer SAP Notes 562863, 361641

With Regards

Ashutosh Chaturevdi

[Former Member · Accepted solution]

Dear Ashutosh,

I found that it's already maintained in SP file:

REMOTE_OS_AUTHENT = TRUE

Regards,

Nilutpal.

[former_member185239 · Accepted solution]

Hi Nilu,

Can you please paste the content for

select * from  "OPS$<SID>ADM".SAPUSER

and also let me know the owner of SAPUSER table.

With Regards

Ashutosh Chaturvedi

[nicholas_chang · Accepted solution]

What about change the password using brconnect?

brconnect -u / -f chpass -o SAPSR3SHD -p <pass>

Cheers,

Nicholas Chang

[Former Member · Accepted solution]

Dear Ashutosh,

Please find the details:

1. SQL> select * from  "OPS$SOLADM".SAPUSER;

USERID

--------------------------------------------------------------------------------

PASSWD

--------------------------------------------------------------------------------

SAPSR3SHD

SAP

2. SQL> SELECT OWNER, TABLE_OWNER, TABLE_NAME FROM DBA_SYNONYMS WHERE SYNONYM_NAME = 'SAPUSER';

OWNER                          TABLE_OWNER

------------------------------ ------------------------------

TABLE_NAME

------------------------------

OPS$SAPSERVICESOL              OPS$SOLADM

SAPUSER

Regards,

Nilutpal.

+91 9766897144

[Former Member · Accepted solution]

Dear Chang,

Yes, I tried to change the password through following command and tried to continue the stage, but didn't get succeeded :-

brconnect -u system/<password of system user> -f chpass -o SAPSR3SHD -p SAP

Regards,

Nilutpal.

[nicholas_chang · Accepted solution]

Hi,

you should put the identical password that you fill when prompt by SAPup.

eg:

[nicholas_chang · Accepted solution]

else, run CREATE_SHDDBCON in SE37 and enter the parameters below:

DBUSER -> schema of your shadow system

DBPASS -> <password of schema>

CONENV -> SID

You can refer to below threads for more info:

http://scn.sap.com/thread/2153909

http://scn.sap.com/thread/3203226

Cheers,

Nicholas Chang

[Former Member · Accepted solution]

Hi Nillutpal,

In the logs attached I can see the entry for variable auth_shadow_upgrade = 1.

Please have a look again at note 400241 in regards to variable auth_shadow_upgrade. According to this note:

"The user is also affected by the variable auth_shadow_upgrade = 1 which, in an upgrade with access to the shadow instance, switches the normal user "sapr3" to "sapr3shd".

This variable must NEVER (not even during an upgrade) be set in the environment or in the registry."

Also refer SAP Note:

Please have a look at 1576837 - ORA-01017: invalid username/password.

Regards,

Sachin

[Former Member · Accepted solution]

Dear All,

Pleased to inform you that after doing changes mentioned in 1519872 note for SAPUPPROF profile, the problem got solved.

Actually after doing oracle upgrade from 10G to 11.2G , the above changes was not done due to which oracle login was not going through.

Thanks a lot to Chang and Ashutosh for your endless help.

Regards,

Nilutpal.

[former_member185239 · Accepted solution]

Dear Nilu,

Congrats. and too learn some good stuff from Sachin Agarwal,Nicholas Chang

Premsukh Bishnoi

With Regards

Ashutosh Chaturvedi