Skip to Content
0

Check DB Job Failing. Invalid System ID

Jul 09, 2017 at 04:55 PM

362

avatar image

Hi All,

We are facing an issue with our DB13 Planning Calendar Job with the below error message

"Invalid system ID"

Now for Update Statistics Job we are getting the below message

As an attempt for the Resolution we have done the following steps

1. Assign the SQLDBA role to BRT$ADM user and executed the Script.

2. Reset the SYSTEM User password which was initially not working

3. Tried to re execute the SSFS Authentication Steps for BRT$ADM user from Database Server level. It got messed up and I reverted back the rsecssfs folders again

4. R3trans -d currently 0000 at the moment.

We have our System upgrade scheduled to be starting from 11.07.2017. So will this scenario be a blocker ?

In the mean time as a work around I executed the update statistics with SYSTEM user and the new password from the back end database.

Now I am trying to find the root cause behind why the System ID is showing invalid and picking up the Production SID. How can I troubleshoot this issue and which configuration do I need to check.

Also the RFC Destination is failing with the below error message

SAPXPG_DBDEST_UNXA0579
ERROR: hostname 'unxa0579' unknown

Thanks and Regard
Anurag Das

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

4 Answers

Prithviraj Rajpurohit Jul 11, 2017 at 01:08 PM
0

Hi Anurag,

Was any refresh activity performed recently? If so, did you perform post-refresh steps?

Check the below mentioned tables to see if the data in the table correspond to the correct system.

SDBAH

SDBAD

SDBAP

SDBAR


Regards,

Prithviraj

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Jul 10, 2017 at 08:59 PM
0

ERROR: hostname 'unxa0579' unknown

Is it a right hostname, if yes why it is not accessible ? Check if you can access it using it's IP address.

Regards,

Harish Karra

Share
10 |10000 characters needed characters left characters exceeded
Reagan Benjamin
Jul 12, 2017 at 10:24 AM
0

Did you check the hostname settings of the RFC SAPXPG_DBDEST_UNXA0579?

Is unxa0579 the hostname of the server where this instance is running?

If this system was refreshed recently then update Oracle Back-end Configuration in DBACOCKPIT

Share
10 |10000 characters needed characters left characters exceeded
Raquel Gomez
Jul 17, 2017 at 12:50 PM
0

Hi Anurag,

Update Statistics Job shows that SXPG_COMMAND_EXECUTE failed.
This is normally related to wrong configuration on RFC Destination "SAPXPG_DBDEST_DBDEST". In your case, RFC Destination "SAPXPG_DBDEST_UNXA0579" is failing with error:
ERROR: hostname 'unxa0579' unknown

Does that hostname 'unxa0579' correspond to DBhost? Is there a Standalone GW running on that DBhost?
You should ensure that hostname 'unxa0579' can be correctly resolved.

Regards,
Raquel

Show 2 Share
10 |10000 characters needed characters left characters exceeded

Hi Raquel,

Apologize again for the late comeback. We were diagnosing this issue only.

The issue is that for some of the systems DB13 Planning Calender Update and Check DB Job is running properly.However in that Systems Database host there is standalone gateway installed.

Motivated by that we did a standalone gateway installation in this particular database host . Now the problem is that we are getting the issue in the generated RFC destination as the below screenshot.

Based on that we have consulted the below Notes
2145145 - User is not authorized to start an external program [VIDEO]
446172 - SXPG_COMMAND_EXECUTE (program_start_error) in DB13

We have maintained the reginfo and secinfo files in the application server under the below path

/usr/sap/SID/Central Instance ID/data
Maintained REGINFO.DAT as P TP=*
and SECINFO.DAT as P TP=* USER=* USER-HOST=* HOST=*

Whereas the Application Server for which the DB13 Planning Calender Jobs are working, there is no REGINFO and SECINFO file maintained.

So trying to figure out what exactly wrong is going on if we have almost same configurations maintained in other systems as well.

I have also compared the tnsnames.ora entries among both the systems (working and not working).
Don't think there is any differences as such except for the working system the host name is fully maintained (FQDN) whereas for the non working system only host name is given.

Kindly suggest if we can try anymore alternative here.

========================
Thanks and Regards
Anurag Das
========================

0

Hi Anurag,

As you correctly found, return code 676 refers to lack of authorization on secinfo file.
And the Notes you pointed out:
2145145 - User is not authorized to start an external program [VIDEO]
446172 - SXPG_COMMAND_EXECUTE (program_start_error) in DB13
also describe this situation.

Check on SM59 settings, which Gateway was been specified. Is the application sevrer GW? Ot the standalone gateway installed on DB host?
In that case, is the secinfo file from that remote GW the one that you need to adjust.
Let me know if RFC still fails after editing it.

Regards,
Raquel

0