cancel
Showing results for 
Search instead for 
Did you mean: 

Install of Linux based NW7.31 using Software Provisioning Manager

Former Member
0 Kudos

Hi Everyone,

I am doing a vanilla install of Netweaver 7.31 on Suse using Oracle 11.2.0.3g Database. I am using the solution manager and don't have access to the server and so am using a remote X server to connect to load up the SWPM. The following are my flow:

Install at hrome Using Remote Software Provisioning Manager:


  • Ran Prerequisite check for 7.31 on Oracle 11g on the system and all came back as Ok.
  • Used Kernel K_720_U_linux_x86_64
  • Installed ALL required prereqs for Oracle 11g
  • Installed Oracle 11.2.0.3 DB
  • Applied patch: SAP_112036_201305_LINX8664.zip and SAP_112036_201306_LINX8664.zip as per Note: 1431799
  • Started the Listener
  • Continued with the NW7.3.1 installer and when it gets to "Create ICM Userstore" It throws this error.

Looking at the logs I found this:

Execution of the command "/usr/sap/NW1/SYS/exe/uc/linuxx86_64/saplikey pf=/usr/sap/NW1/SYS/profile/NW1_DVEBMGS00_suse1 -install_first_temp VXXXXXXXXXX XXXXXX" finished with return code 2. Output:

saplikey: failed to connect to the database.

When I run this command on the console with a trace=2, I also get "failed to connect to the database"

/usr/sap/NW1/SYS/exe/uc/linuxx86_64/saplikey pf=/usr/sap/NW1/SYS/profile/NW1_DVEBMGS00_suse1 -install_first_temp VXXXXXXXXXX XXXXXX trace=2

Error in the trace logs indicates:

RSecSSFs: Exiting function "RSecSSFsGetRecord" with return code 1 (message: Record with key "DB_CONNECT/DEFAULT_DB_CON_ENV" not found in secure storage) [rsecssfs.c 897]

read_ssfs_record(): RSecSSFsGetRecord(DB_CONNECT/DEFAULT_DB_CON_ENV)=1 : Record with key "DB_CONNECT/DEFAULT_DB_CON_ENV" not found in secure storage

read_con_info_ssfs(): deregister callback ssfs_dbi_trace

-->DbSlConnect(vers=0, type=0, env='[default env]', userid='SAPSR3')

Register application info.

Oracle client version: 11.2.0.3.0, V1, default build, (dbsl 720 081211, UNICODE[2])

Installed Oracle client patches:

# Patch  13508485     : Created on 21 Dec 2011, 13:23:38 hrs PST8PDT

# Patch Description: Created on  3 Jan 2012, 02:50:27 hrs PST8PDT

# Patch  11742262     : Created on  7 Mar 2012, 12:22:41 hrs CET

  Default connection: tnsname ='NW1'

-->oci_initialize(con=0, char='UTF16', nchar='AL16UTF16', nls=-1),uc_ln=2

Tue Jul 30 10:11:01 2013

OCIEnvCreate(mode=16384=OCI_UTF16) returned 0 (for default NLS handle)

   OCIHandleAlloc(OCI_HTYPE_ERROR, con=0, ErrHp=123e7c0)

   OCIHandleAlloc(OCI_HTYPE_ERROR, con=0, ErrBt=123fab0)

NLS env. settings: lang=41004D00450052004900430041004E00

                   terr=41004D0045005200490043004100

                   char=55005400460031003600

Client NLS setting (by OCINlsGetInfo(con=0)): 'AMERICAN_AMERICA.UTF16'

charset='UTF16', ncharset='AL16UTF16', UNI_ASC=FALSE

Connecting as SAPSR3/<pwd>@NW1 on connection 0 (nls 0) ... (dbsl 720 081211, UNICODE[2])

   OCIHandleAlloc(OCI_HTYPE_SVCCTX, con=0, svchp=123f9d0)

Allocating server context handle

Attaching to database server NW1 (con=0, svchp=123f9d0, srvhp=1242e98)

Tue Jul 30 10:11:02 2013

Assigning server context 1242e98 to service context 123f9d0

   OCIHandleAlloc(OCI_HTYPE_SESSION, con=0, usrhp=1281e28)

Assigning username to user session: con=0, usrhp= 1281e28

Assigning password to user session: con=0, usrhp=1281e28

Starting user session: OCISessionBegin(con=0, usr='SAPSR3', svc=123f9d0, srv=1242e98, usr=1281e28)

   OCISessionBegin(OCI_DEFAULT) failed with -1=OCI_ERROR

   OCISessionBegin(OCI_DEFAULT) failed with SQL error 1017:

   ORA-01017: invalid username/password; logon denied                                                                       

*** ERROR => CONNECT failed with sql error '1017'

[dbsloci.c    14533]

   set_ocica() -> SQL error code 1017

-->oci_get_errmsg (con=0, rc=1017)

   OCIErrorGet -> SQL error code: 1017

   ORA-01017: invalid username/password; logon denied                                                                       

   DbSlConnect(con=0) -> orc=0, 99=DBSL_ERR_DB

***LOG BY2=> sql error 1017   performing CON [dblink       540]

***LOG BY0=> ORA-01017: invalid username/password; logon denied [dblink       540]

*** ERROR => saplikey: failed to connect to the database. [saplikey_w.c 762]

So from here, I can see its not a saplikey issue but a database connection issue. I have tried doing:

> R3trans -d

This is R3trans version 6.22 (release 720 - 18.11.11 - 11:29:00).

unicode enabled version

2EETW169 no connect possible: "DBMS = ORACLE                           --- dbs_ora_tnsname = 'NW1'"

R3trans finished (0012).

What concerns me about the trace is: read_ssfs_record(): RSecSSFsGetRecord(DB_CONNECT/DEFAULT_DB_CON_ENV)=1 : Record with key "DB_CONNECT/DEFAULT_DB_CON_ENV" not found in secure storage.

Suggestions?

Cheers,

Thusjanthan Kubendranathan

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

Replace an new kernel mentioned in the note:1680045.

in the install master of NW731, sap suggest use Software Provisioning Manager 1.0 to do installation. I used the new 720 EXT kernel instead of old one and the installation process complete successfully.

Thanks

Rishi Abrol

Answers (7)

Answers (7)

tamil_arasan
Active Contributor
0 Kudos

Dear All,

Instead of maually switching the kernel 7.20 EXT then executing the above command, do the following,

1. Download the latest 7.20 EXT kernel

2. During the installation( in the kernel extraction screen), uncheck default kerenel and give the downloaded new kernel 7.20 EXT path and proceed.

it won't throw error in the phase "Create ICM Userstore"

Cheers,

Pradeep

tamil_arasan
Active Contributor
0 Kudos

Thanks Akshay,

We have done 7.20 EXT kernel replacement and done this command execution rsecssfx put DB_CONNECT/DEFAULT_DB_PASSWORD <password> then the installtion was completed successfully.

Thanks once again and sorry for belated update.

Cheers,

Pradeep

Former Member
0 Kudos

Thanks Pradeep, my issue get resolved too by executing the command above.

Regards,

Ladislao

Former Member
0 Kudos

Thanks Guys, my issue also got resolved by executing the same command

rsecssfx put DB_CONNECT/DEFAULT_DB_PASSWORD <password>


Regard

Ravi

tamil_arasan
Active Contributor
0 Kudos

Dear All,

I am facing the same issue. I have changed the DBINDEP andd DBDEP kerenels however it is not successful so far. i have tried DBSL as well but no luck. System details. SAP NW731 in Windows 2008.

Anyone please give your suggestions?

Thanks,

Pradeep

Akshay_G
Contributor
0 Kudos

What is the error that you are getting?

ORA-01017 Invalid Username/Password?

Are you using "@" anywhere in the master password or any other password defined during installation.

Which kernel did you use?

Regards,

Akshay

tamil_arasan
Active Contributor
0 Kudos

Dear Akshay,

yes, master password has @ symbol. I have used 720_EXT kernel.

Error is saplikey:Failed to connect to the database

kindly give your suggestion.

Thank you very much!

Regards,

Pradeep

Akshay_G
Contributor
0 Kudos

Please dont use "@" in the password.

Its a well known issue, when you use "@" in the password the kernel confuses @ in the password string as connection identifier and prevents from establishing a successful connection.

You may have to start the installation with other password (non @ specific) and it should hopefully go through.

Regards,

Akshay

pavan_anjimeti
Participant
0 Kudos

Hi Thusjanthan,

This is issue with Database Library(DBSL). SAP released latest patch 439(lib_dbsl_439-10007263.sar)

Please try with DBSL 439

Regards,

Pavan

former_member185239
Active Contributor
0 Kudos

Hi Thusjanthan,

Follow the below sapnote to resolve your issue.

1576837 - ORA-01017: invalid username/password

With Regards

Ashutosh Chaturvedi

Akshay_G
Contributor
0 Kudos

Check note 400241 for DB Connect failed error "ORA-01017: invalid username/password; logon denied"

-Akshay

karthikeyan_natarajan4
Active Contributor
0 Kudos

Hi,

Please check status of your database is up and running.

error shows

ORA-01017: invalid username/password; logon denied                                                                   

Please check the schema user ID is locked or not SAPSR3

and also please attach us the trans.log file.

Refer to this thread, same issue was discussed and solved by using the latest kernel

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

regards

kartik