cancel
Showing results for 
Search instead for 
Did you mean: 

SWPM Connect via SAPUSER not longer supported

Kingfo
Explorer
0 Kudos

Hi Gurus,

When doing an export preparation we got an error in step check the db connection, R3load log listed as below:

(BLD) INFO: kernel release 745 [UNICODE]

(BLD) INFO: data format 1.8

(BLD) INFO: patch number 100

(BLD) INFO: compiled on "Feb 26 2016 15:45:50"

(PRC) INFO: working directory "/tmp/sapinst_instdir/NW740/ORA/COPY/EXP/AS-ABAP/PREEXP"

(PRC) INFO: called "/usr/sap/PAX/D11/exe/R3load -testconnect"

(PRC) INFO: process id 23014

(LOG) INFO: log level: 1

(LOG) INFO: log format: classic

DbSl Trace: Connect via SAPUSER not longer supported.

(DB) ERROR: db_connect rc = 256

DbSl Trace: Connect via SAPUSER not longer supported.

(DB) ERROR: DbSlErrorMsg rc = 29

We had changed the method with SSFS long time ago and it works without problem manually.

/usr/sap/PAX/D11/exe/R3load -testconnect

/usr/sap/PAX/D11/exe/R3load: START OF LOG: 20160913101853

(BLD) INFO: sccsid "@(#) $Id: //bas/745_STACK/src/R3ld/R3load/R3ldmain.c#4 $ SAP"

(BLD) INFO: kernel release 745 [UNICODE]

(BLD) INFO: data format 1.8

(BLD) INFO: patch number 100

(BLD) INFO: compiled on "Feb 26 2016 15:45:50"

(PRC) INFO: working directory "/home/pjxadm"

(PRC) INFO: called "/usr/sap/PAX/D11/exe/R3load -testconnect"

(PRC) INFO: process id 23452

(LOG) INFO: log level: 1

(LOG) INFO: log format: classic

(DB) INFO: connected to DB

(DB) INFO: disconnected from DB

How can i resolve this issue?Latest SWPM tool(SWPM 1.0 SP17 for NW higher than 7.0x) is used. Any comments are appreciated.

Regards,

Feng

Accepted Solutions (0)

Answers (4)

Answers (4)

Kingfo
Explorer
0 Kudos

Thanks all your quick response.

I had checked the ENV for user sidadm before, we have default csh and variables are there as well.

Tnsping is working and manual check without error under user <sid>adm.

Other ideas?

former_member227283
Active Contributor
0 Kudos

Hi,

Enable the trace for R3load referring to below note and then retry the Export.

2361489 - Enabling DBSL traces in R3load

Regards,

Anil Bhandary

Kingfo
Explorer
0 Kudos

Enabled and can see the trace when manually executed but can't see details within Export log (R3load.exe.log), i did a restart run, any thoughts?

Former Member
0 Kudos

Hello Hu,

Could you provide the following just as a cross check:

1. grep paxadm /etc/passwd

2. upload the sapinst_dev log file

3. run "env" when logged on as paxadm and post the output here as well.

KR,

Amerjit

former_member227283
Active Contributor
0 Kudos

Did you set the environment variable for trace in Shell file or your set it through manually using command ?

If you have set env by manual command not in shell file, then SWPM will not pick the env as it make user switch internally and manual setting of env will not be known to user.

You have to set that in shell file after that logout from user and login again and check if env still exists. If yes then try to call SWPM from scratch and let us know whether trace has been generated or not.

Kingfo
Explorer
0 Kudos

It's set permanently in user environment variable but seems SWPM will not pick the env, even i call SWPM from scratch it doesn't work. Don't know if we can check this or change it somewhere for the SWPM tool.

former_member227283
Active Contributor
0 Kudos

Can you perform the steps in RESOLUTION section of the below SAP note and confirm all is good and you are not seeing any issue as mentioned in the note.

1875902 - R3load -testconnect fails during system export

Regards,

Anil

former_member227283
Active Contributor
0 Kudos

Pls share the output of step by step command which you follow as per the note.

Sriram2009
Active Contributor
0 Kudos

Hi Kindfo.

On Source system export you have to use the user id SIDADM. and also refer the SAP system copy guide based on your OS / DB & SAP version

https://cp.hana.ondemand.com/dps/d/preview/ec5624d5073d4c949b42bf284742748d/1.0/en-US/frameset.htm

BR

SS

former_member227283
Active Contributor
0 Kudos

Hi,

Follow the below steps and provide the output.

1. Login to server with SIDADM

2. Run command CSH after login with SIDADM

3. Run command ENV and share the output of ENV

Basically need to see the the SSFS parameter is enabled or not in C SHELL, Earlier I faced similar problem and found SSFS parameter was not enabled in C SHELL.

Regards,

Anil Bhandary

former_member182967
Active Contributor
0 Kudos

Hi Kingfo,

What can use see after setting environment variable rsdb_ssfs_connect=1 and restart SWPM.

Regards,

Ning

Former Member
0 Kudos

Hi,

Try this step..

cmd>tnsping <sid>

then retry.