Error during the SAP System Copy - Start Instance phase (ORA-01017: invalid username/password; logon denied)

[joo_migueldimas]

Hello,

DB: Oracle 11.2g (11.2.0.4)

OS: Windows Server 2012 (R2)

I´m doing a homogeneous system copy and during the target server installation/copy, the software provisioning manager stopped with an error during the phase "Start Instance":

I checked the SAPMMC console and in fact the disp+work.EXE is stopped (with grey color).

I checked the log file dev_disp and I see the following error:

...
Mon Mar 14 16:27:59 2016
*** ERROR => DpHdlDeadWp: W9 (pid 3912) died (severity=0, status=0) [dpxxwp.c     1746]
...

Then I checked the dev_w9 log file and I see the following errors:

...
C  
C Mon Mar 14 16:26:47 2016
C     OCISessionBegin(OCI_DEFAULT) failed with SQL error 1017:
C     ORA-01017: invalid username/password; logon denied                                                                            
C  OCISessionBegin(con=0, svc=035BEA60, srv=035C2120='DEV'): start session usr=035D1260='SAPSR3', rc=1017
C  OCIHandleFree(con=0, svc=035BEA60): Free session hdl usr=035D1260
C  OCIServerDetach(stale2 con=0, svc=035BEA60, srv=035C2120='DEV') successfully detached
C  OCIHandleFree(con=0, svc=035BEA60): Server handle srv=035C2120 freed
C  OCIHandleFree(con=0): Service svc=035BEA60 freed (i=0).
C  rc=1017 -> Trying to reattach to server 'DEV'
C  OCIHandleAlloc(con=0): Service svc=035BEA60 created, rc=0
C  OCIServerAttach(con=0, svc=035BEA60): New server hdl. srv=035C2120 attached to 'DEV'
C  
C Mon Mar 14 16:27:49 2016
C     OCISessionBegin(OCI_DEFAULT) failed with SQL error 3113:
C     ORA-03113: end-of-file on communication channel                                                                               
C  OCISessionBegin(con=0, svc=035BEA60, srv=035C2120='DEV'): start session usr=035D1260='SAPSR3', rc=3113
C  OCIHandleFree(con=0, svc=035BEA60): Free session hdl usr=035D1260
C  OCIServerDetach(stale2 con=0, svc=035BEA60, srv=035C2120='DEV') successfully detached
C  OCIHandleFree(con=0, svc=035BEA60): Server handle srv=035C2120 freed
C  OCIHandleFree(con=0): Service svc=035BEA60 freed (i=1).
C  *** ERROR => CONNECT failed with SQL error '3113'
 [dbsloci.c    16104]
B  ***LOG BV3=> severe db error 3113; work process is stopped [dbsh         1241]
B  ***LOG BY2=> sql error 3113   performing CON [dblink       544]
B  ***LOG BY0=> ORA-03113: end-of-file on communication channel [dblink       544]
M  ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c   1538]
M  in_ThErrHandle: 1
M  *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c   11614]
M  
M  Info for wp 9
...

I also ran the R3trans -d with <sid>adm operation system user and I also see the same errors:

4 ETW000 r3trans version 6.24 (release 721 - 31.07.15 - 14:39:42).
4 ETW000 ===============================================
4 ETW000 
4 ETW000 date&time   : 14.03.2016 - 16:24:18
4 ETW000 control file: <no ctrlfile>
4 ETW000 R3trans was called as follows: r3trans -d
4 ETW000  trace at level 1 opened for a given file pointer
4 ETW000  [     dev trc,00000]  Mon Mar 14 16:24:18 2016
4 ETW000  [     dev trc,00000]  Loading DB library 'dboraslib.dll' ...
4 ETW000  [     dev trc,00000]  Mon Mar 14 16:24:19 2016
4 ETW000  [     dev trc,00000]  Library 'dboraslib.dll' loaded
4 ETW000  [     dev trc,00000]  Version of 'dboraslib.dll' is "721.02", patchlevel (0.600)
4 ETW000  [     dev trc,00000]  con_info_ext_support(): DBSL supports extended connect protocol
4 ETW000                          ==> connect info for default DB will be read from ssfs
4 ETW000  [     dev trc,00000]  dbs/ora/stmt_cache_size = 250
4 ETW000  [     dev trc,00000]  Register application info.
4 ETW000  [     dev trc,00000]  Mon Mar 14 16:24:20 2016
4 ETW000  [     dev trc,00000]  Oracle client version: 11.2.0.4.0, (dbsl 721 180915, non-unicode)
4 ETW000  [     dev trc,00000]  Detailed Oracle client (patch) info not available.
4 ETW000  [     dev trc,00000]  Mon Mar 14 16:24:22 2016
4 ETW000  [     dev trc,00000]  Client NLS setting (by OCINlsGetInfo(con=0)): 'AMERICAN_AMERICA.WE8DEC'
4 ETW000  [     dev trc,00000]  Connecting as SAPSR3/<pwd>@DEV on connection 0 (nls 0) ... (dbsl 721 180915, non-unicode)
4 ETW000  [     dev trc,00000]  OCIHandleAlloc(con=0): Service svc=04132B40 created, rc=0
4 ETW000  [     dev trc,00000]  Mon Mar 14 16:24:25 2016
4 ETW000  [     dev trc,00000]  OCIServerAttach(con=0, svc=04132B40): New server hdl. srv=04136190 attached to 'DEV'
4 ETW000  [     dev trc,00000]  Mon Mar 14 16:24:36 2016
4 ETW000  [     dev trc,00000]     OCISessionBegin(OCI_DEFAULT) failed with SQL error 1017:
4 ETW000  [     dev trc,00000]     ORA-01017: invalid username/password; logon denied                                                                            
4 ETW000  [     dev trc,00000]  OCISessionBegin(con=0, svc=04132B40, srv=04136190='DEV'): start session usr=041451D0='SAPSR3', rc=1017
4 ETW000  [     dev trc,00000]  OCIHandleFree(con=0, svc=04132B40): Free session hdl usr=041451D0
4 ETW000  [     dev trc,00000]  OCIServerDetach(stale2 con=0, svc=04132B40, srv=04136190='DEV') successfully detached
4 ETW000  [     dev trc,00000]  OCIHandleFree(con=0, svc=04132B40): Server handle srv=04136190 freed
4 ETW000  [     dev trc,00000]  OCIHandleFree(con=0): Service svc=04132B40 freed (i=0).
4 ETW000  [     dev trc,00000]  rc=1017 -> Trying to reattach to server 'DEV'
4 ETW000  [     dev trc,00000]  OCIHandleAlloc(con=0): Service svc=04132B40 created, rc=0
4 ETW000  [     dev trc,00000]  OCIServerAttach(con=0, svc=04132B40): New server hdl. srv=04136190 attached to 'DEV'
4 ETW000  [     dev trc,00000]  Mon Mar 14 16:24:46 2016
4 ETW000  [     dev trc,00000]     OCISessionBegin(OCI_DEFAULT) failed with SQL error 1017:
4 ETW000  [     dev trc,00000]     ORA-01017: invalid username/password; logon denied                                                                            
4 ETW000  [     dev trc,00000]  OCISessionBegin(con=0, svc=04132B40, srv=04136190='DEV'): start session usr=041451D0='SAPSR3', rc=1017
4 ETW000  [     dev trc,00000]  OCIHandleFree(con=0, svc=04132B40): Free session hdl usr=041451D0
4 ETW000  [     dev trc,00000]  OCIServerDetach(stale2 con=0, svc=04132B40, srv=04136190='DEV') successfully detached
4 ETW000  [     dev trc,00000]  OCIHandleFree(con=0, svc=04132B40): Server handle srv=04136190 freed
4 ETW000  [     dev trc,00000]  OCIHandleFree(con=0): Service svc=04132B40 freed (i=1).
4 ETW000  [dbsloci.c   ,00000]  *** ERROR => CONNECT failed with SQL error '1017'
4 ETW000  [     dev trc,00000]  Mon Mar 14 16:24:47 2016
4 ETW000  [    dblink  ,00000]  ***LOG BY2=>sql error 1017   performing CON
4 ETW000  [    dblink  ,00000]  ***LOG BY0=>ORA-01017: invalid username/password; logon denied
2EETW169 no connect possible: "DBMS = ORACLE                           --- dbs_ora_tnsname = 'DEV'"

I already faced this ORA error in other situations but know I can´t understand what is wrong and how to correct it!

I read the sap note 1576837 - ORA-01017: invalid username/password; but I can´t understand which scenario applies to my specific case!

I checked the database users (select username, account_status from dba_users;) and I don´t see anything wrong :

Any tips? Can you help me please to understand what is wrong here and how to correct this error?

Kind regards,

Thank you,

João Dimas

[Former Member · Accepted solution]

Hallo,

you are using SSFS to authenticate SAPSR3 as indicated by the trace file:

connect info for default DB will be read from ssfs

Hence I believe note 1576837 does not apply because SSFS doesn't use table SAPUSER anymore.

You can set the password of user SAPSR3 in a SSFS environment using the following command:

brconnect -u system/<system_pwd> -c -f chpass -o SAPSR3 -p <sapsr3_pwd> -s abap –RDB

I suggest you first check if SSFS is correctly configured in the environment. Please refer to:

1639578 - SSFS as password store for primary database connect

1622837 - Secure connection of AS ABAP to Oracle via SSFS

Regards

Thomas.

[joo_migueldimas · Accepted solution]

Hello Thomas,

Yes... but I think there is something wrong here because when I check the sapowner of this DB is not SAPSR3!! The sapowner is SAPR3

SELECT OWNER FROM DBA_TABLES WHERE TABLE_NAME = 'T000';

It´s a little bit strange because I believe the sap owner must be SAPSR3 user and not SAPR3, in Oracle DB 11.2g version! I don´t know exactly...

This is a SAP ERP 6.0 NUC X64 with 721 EXT kernel version! I gave that Kernel Media in the SWPM tool installation wizard.

Any tips?

Thank you,

João Dimas

[joo_migueldimas · Accepted solution]

Hello Thomas again,

I read both sap notes that you recommended but unfortunately I´m with some doubts regarding some things about Oracle DB.

Do you read my previous message?... because I´m with some doubts regarding that specific subject, the ORACLE database users! I see that I have those two oracle users, the SAPR3 and the SAPSR3 and as I realize, I must consider the "new method" by using the SSFS method, therefore I believe this method use the SAPSR3 user... am I correct? Because, as I wrote before, my database has the owner SAPR3, I believe this is not correct! Am I right? If so, how to change the owner of my oracle database from SAPR3 to SAPSR3?

During the software provisioning manager tool, one screen was this one that I show you bellow and I inserted the SAPSR3 user! Do you think I did wrong?! Do you think should inserted in that field the value SAPR3 instead SAPSR3?

Kind regards,

João Dimas

[Sriram2009 · Accepted solution]

Hi Joao.

1. Are you using the SAP kernel 7.21 Ext? If it is not you can download the latest kernel & Dbsl patches 7.21 latest level from SAP SMP.

2. Attach the SAPinst log

Regards

SS

[Former Member · Accepted solution]

Hallo João

do I understand you correctly that you changed the screen entry from SAPR3 to SAPSR3?

You are correct that the standard user is SAPSR3. However, you are performing a system copy hence the schema owner depends on you source database as well as your copy procedure.

My understanding is that the schema can only be changed if you perform a system copy using export/import. If you use backup/restore (which is most widely used) you can not change the schema.

Conclusion: Assuming you are using backup/restore to perform your system copy, you shouldn't have adjusted the ABAP schema owner but should have kept SAPR3.

Regards

Thomas.

[joo_migueldimas · Accepted solution]

Hello SS,

1. Are you using the SAP kernel 7.21 Ext? If it is not you can download the latest kernel & Dbsl patches 7.21 latest level from SAP SMP.

Yes, I give the kernel media 7.21 EXT NUC (x64) to Software Provisioning Manager tool (number of kernel media: 51050695_2). The patch level is 600 as you see in the following image:

2. Attach the SAPinst log

Please see the log file attached to this message.

The other log files, you may check it in the first message that I posted here.

Best regards,

João Dimas

sapinst.txt.zip

[joo_migueldimas · Accepted solution]

Hello Thomas,

Really?!

Yes, this is a system copy using the backup/restore method.

So... how can I keep the "old method"?... I mean, how can I change the oracle database authentication method in order to disable the SSFS authentication and set the standard/old method authentication? Can you tell me please?

Thank you,

João Dimas

[Former Member · Accepted solution]

Hallo,

In the screen you posted, you have to keep SAPR3 and not change to SAPSR3.

The SSFS mechanism is than build using that user (SAPR3).

As outlined in note 1622837 the SSFS mechanism is using keyword DB_CONNECT/SHADOW_DB_USER to identify which user to use to connect to the database.

So your solution should be to keep user SAPR3 during your installation process.

Have you confirmed that SAPR3 is the ABAP schema in your source database?

Regards

Thomas.

[Sriram2009 · Accepted solution]

Hi Joao.

On Windows OS level could you check the Oracle DB service status? if it is not started you can start manually and then retry system copy where its stooped.

Regards

SS

[joo_migueldimas · Accepted solution]

Hello Thomas,

In the screen you posted, you have to keep SAPR3 and not change to SAPSR3.
The SSFS mechanism is than build using that user (SAPR3).

As outlined in note 1622837 the SSFS mechanism is using keyword DB_CONNECT/SHADOW_DB_USER to identify which user to use to connect to the database.

So your solution should be to keep user SAPR3 during your installation process.

So... you are telling me to stop/cancel this installation process and restart again the software provisioning manager from the scratch, am I right? Can I do that from this point...? I mean, I believe there are a lot of thing that were created during the installation activity, at the database level and also in OS level, so I´m afraid to restart this installation from the scratch! This is my concerns about it.

Have you confirmed that SAPR3 is the ABAP schema in your source database?

How can I confirm that? The schema is the same of database owner, am I right?

I only know one way to check that information, is the output of the following SQL Plus command (SELECT OWNER FROM DBA_TABLES WHERE TABLE_NAME = 'T000';):

Best regards,

João Dimas

[joo_migueldimas · Accepted solution]

Hello SS,

Everything is running Sriram.

Best regards,

João Dimas

[Former Member · Accepted solution]

Hallo,

yes, the SELECT shows your schema owner to be SAPR3. Another way is to login to SAP --> System --> Status:

The "Database data" is in the left bottom of the screen and will also show the owner.

My understanding is that the only supported way to change the schema owner is to run an export/import the database.

So based on what you've told here, I suggest to restart your installation.

Regards

Thomas,

[joo_migueldimas · Accepted solution]

Hello Thomas,

Yes, I know that is another way to check the SAP owner, but don´t forget that at this moment I don´t have SAP, it doesn´t start well... that was the main error, the error that I reported here.

Ok... I´m trying to contact SAP support to know more details about this situation... so I will update this message as soon I have more details about it.

Best regards,

João Dimas

[Former Member · Accepted solution]

Hallo,

you need to check the owner in the SOURCE system which I assumed is still running.

If the owner in the SOURCE system is SAPR3 than you will need to use SAPR3 in the copied system as well when you build via backup/restore.

Regards

Thomas.

[Reagan]

If the source system is setup with the schema name as SAPR3 then you have to keep that as the schema name when you are doing a system copy using backup and restore method. The backup and restore method does not allow you to change the schema name. if you want to change the schema name from SAPR3 to SAPSR3 then you should do an export and import of the database using R3load. There is no such schema name restriction for SSFS configuration. You should be able to configure SSFS with the existing schema name. I believe you no longer have the sapinst screen where you can input the schema name. In that case the best option would be to restart the target system creation from the beginning as the schema name is maintained in many places like profiles, environment variable, installation control files and changing that to SAPR3 would require a lot of manual work.

[joo_migueldimas]

Hello Reagan Benjamin,

Hum ok...

But tell me, as I told to Thomas Dierkes, can I do that from this point...? I mean, I believe there are a lot of things that were created during this installation process activity, for example at the database level and also in OS level too, so I´m afraid to restart this installation from the scratch!

What do you think? No problem with that?

Best regards,

João Dimas

[Former Member]

Hallo,

SWPM menus should give you the option to stop the installer. When you restart SWPM select "Run a new option".

I don't know your infrastructure: if it would be me I would just commission the (virtual) server again and start from scratch.

Regards

Thomas.

[Reagan]

If you restart sapinst it will provide you two options. Continue with old option and Start a new run. If you select continue with the old option it will not let you modify any of the entries you have supplied before. The only way you can change SAPSR3 to SAPR3 is by manually editing all the sapinst control files, profiles a environment variables. The best would be to start the target system creation once again. It saves you from further issues.

[joo_migueldimas]

Hello Reagan and Thomas,

Yeah I know that, I already done a lot of installations and migrations... my concerns is because this is an Oracle database and besides of that I´m in the phase 23 of 26, which means that a lot of things happened, loaded and were created at database and OS levels during this installation process.

But OK... I will follow your recommendations. I will update this message as soon I have more details about it.

Thank you,

João Dimas

[joo_migueldimas]

Hello,

Solved!

I already solved the error! As I said before, in my previous message, I restarted the installation and in the oracle database screen, where it asks for the schema value, I inserted the SAPR3 schema instead of SAPSR3 and so with this change the installation finish without errors!

I will close this message but before I need to ask you one more thing if you don´t mind that is related with this new way to connect the SAP to the Oracle DB... tell me please if this is mandatory to do if I want to upgrade this Oracle DB from 11.2g to 12.1c! Because in software provisioning manager it inform the following:

"Database Schema Parameters The new default for ABAP Schema is SAPSR3. As of Oracle server version 12.1, ABAP SSFS is set automatically.".

So... this conversion from the "old connection method" (with SAPR3) to the "new connection method" (SSFS) is mandatory or not? And if so, we need to perform that conversion before the Oracle upgrade manually or it will do automatically?

Thank you,

Best regards,

João Dimas

[Former Member]

Hallo,

I think you are still confusing the ABAP schema owner with SSFS.

As outlined above and in the note I mentioned twice: SSFS doesn't care who owns the schema. For SSFS it's just a user name.

SSFS is a prerequisite for Oracle 12 but you shouldn't worry because you are already using it.

This is indicated by "connect info for default DB will be read from ssfs" in trans.log. Refer to one of my first responses above.

Just execute "R3trans -x" and check trans.log if you want to try it again. If trans.loog indicates you are using OPS$ then you have to convert to SSFS before you upgrade to Oracle 12.

The note mentioned before will tell you how to do this.

The only thing different to a standard configuration in your configuration is the ABAP schema which is SAPR3 vs SAPSR3.

You can only change the owner if you execute an export/import but the update to Oracle 12 doesn't care if you have SAPR3 or SAPSR3.

Regards

Thomas.

[Reagan]

SSFS replaced the old OPS$ mechanism. It has nothing to do with the schema name. Oracle 12c is supported with newer kernel releases. The latest kernel releases only support SSFS functionality. SAPSR3 is the standard naming convention for an ABAP schema. It doesn't mean SSFS will only work with SAPSR3. During the installation/system copy sapinst will setup the target system with SSFS if the database release is 12c.

[joo_migueldimas]

Hello Thomas and Reagan,

You´re right! Sorry for my confusing!

Many thanks for the clarification and the explanation

Thank you,

Best regards,

João Dimas