cancel
Showing results for 
Search instead for 
Did you mean: 

Authentication error at the start of Import ABAP phase during Installation

0 Kudos

Hello All,

I am importing ECC application on a newly installed HANA DB

with the latest version of 1.0 SPS10 REV 102. During the import I am

facing an issue right at the start of the import ABAP phase where I am

getting an authentication error as per the logs shown below:

*********

Execution of the command

"/tmp/sapinst_exe.27660.1444398180/jre/bin/java-classpath

migmon.jar:migmonctrl.jar:ngdbc.jar -showversion -Xmx1024m

com.sap.inst.migmon.imp.ImportMonitor -sapinst -host

-instanceNumber 00 -username SAPAHD -readPasswordFromStdin

-databaseNameAHD" finished with return code 101. Output:

java version "1.6.0_101"

Java(TM) SE Runtime Environment (build 6.1.080)

SAP Java Server VM (build 6.1.080 25.51-b02, Aug 6 2015 17:24:33 -

61_REL - optU - linux amd64 - 6 - bas2:247116 (mixed mode))

com.sap.inst.migmonctrl.exception.MigmonCtrlException:

com.sap.inst.migmonctrl.exception.MigmonCtrlException:

com.sap.db.jdbc.exceptions.jdbc40.SQLInvalidAuthorizationSpecException:

[10]: authentication failed

at

com.sap.inst.migmonctrl.imp.database.JdbcConnection.createConnection(JdbcConnection.java:77)

at

com.sap.inst.migmonctrl.imp.database.JdbcConnection.get(JdbcConnection.java:138)

at

com.sap.inst.migmonctrl.imp.database.JdbcConnection.prepareQuery(JdbcConnection.java:176)

at

com.sap.inst.migmonctrl.imp.database.JdbcConnection.executeQuery(JdbcConnection.java:191)

at

com.sap.inst.migmonctrl.MigmonCtrlImport.initializeConnection(MigmonCtrlImport.java:296)

at

com.sap.inst.lib.migmonctrl.MigmonCtrlFactory.getInstance(MigmonCtrlFactory.java:60)

at

com.sap.inst.migmon.imp.ImportMonitor.startAppJob(ImportMonitor.java:440)

at

com.sap.inst.lib.app.CommandLineApp.doMain(CommandLineApp.java:116)

at

com.sap.inst.migmon.imp.ImportMonitor.main(ImportMonitor.java:484)

Caused by: com.sap.inst.migmonctrl.exception.MigmonCtrlException:

com.sap.db.jdbc.exceptions.jdbc40.SQLInvalidAuthorizationSpecException:

[10]: authentication failed

at

com.sap.inst.migmonctrl.imp.database.JdbcConnection.establishConnection(JdbcConnection.java:118)

at

com.sap.inst.migmonctrl.imp.database.JdbcConnection.createConnection(JdbcConnection.java:59)

... 8 more

Caused by:

com.sap.db.jdbc.exceptions.jdbc40.SQLInvalidAuthorizationSpecException:

[10]: authentication failed

at

com.sap.db.jdbc.exceptions.jdbc40.SQLInvalidAuthorizationSpecException.createException(SQLInvalidAuthorizationSpecException.java:40)

at

com.sap.db.jdbc.exceptions.SQLExceptionSapDB.createException(SQLExceptionSapDB.java:301)

at

com.sap.db.jdbc.exceptions.SQLExceptionSapDB.generateDatabaseException(SQLExceptionSapDB.java:185)

at

com.sap.db.jdbc.packet.ReplyPacket.buildExceptionChain(ReplyPacket.java:102)

at

com.sap.db.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:1030)

at

com.sap.db.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:820)

at

com.sap.db.util.security.AbstractAuthenticationManager.connect(AbstractAuthenticationManager.java:43)

at

com.sap.db.jdbc.ConnectionSapDB.openSession(ConnectionSapDB.java:569)

at

com.sap.db.jdbc.ConnectionSapDB.doConnect(ConnectionSapDB.java:421)

at

com.sap.db.jdbc.ConnectionSapDB.<init>(ConnectionSapDB.java:174)

at

com.sap.db.jdbc.ConnectionSapDBFinalize.<init>(ConnectionSapDBFinalize.java:13)

at com.sap.db.jdbc.Driver.connect(Driver.java:235)

at java.sql.DriverManager.getConnection(DriverManager.java:582)

at java.sql.DriverManager.getConnection(DriverManager.java:185)

at

com.sap.inst.migmonctrl.imp.database.JdbcConnection.establishConnection(JdbcConnection.java:109)

*******************

I tried to login with the SAPAHD user to the

HANA DB(both HANA Studio and HDBSQL) and the login was successful and I do not see any

authentication issues with respect to this users to the HANA DB.

Kindly help me to check on this.

Regards,

Krishna

Accepted Solutions (1)

Accepted Solutions (1)

shriramcse
Participant
0 Kudos

Hi Krishna,

Create the SAP<SID> in your case SAPAHD ,in the System DB. And repeat the phase.

BR,

Sriram

0 Kudos

Hello Sriram,

Thank you.

Yes creating the same schema user in System DB with the same password as in tenant worked and that helped to proceed with the import.

However this needs to be validated by SAP as i am not sure why its expecting the same schema user in System DB when the actual schema is created in a tenant.

Regards,

Krishna

former_member183326
Active Contributor
0 Kudos

Hello,

I would not recommend this method. The systemdb is not intended to be used for importing application schemas and for a supported installation you would have to import into a tenant (when the is fix available of course)

I would recommend anyone reading this thread to wait for the official fix from SAP.

I will update this thread once a fix has been issued.

Best Regards,

Michael

0 Kudos

Hello Michael,

Yes this certainly is not a permanent fix and is only a work around.

Also I have checked the application schema and it is created only in the tenant DB and not the System DB. Just that the schema user is created in both the Tenant DB (created by installer) and System DB(Created Manually) .

Regards,

Krishna

shriramcse
Participant
0 Kudos

Hi Michael,

User should be created automatically in the System DB as well, this is Standard in all DB not only in HANA( user will present in both system and also in APP DB). Due to bug in tool it not create user in system DB , creating user in system DB will not create any issue as tool missed to create.

Do you have Multi tenant DB ?if so can you check is user present in both places or not ?

BR,

Sriram

former_member183326
Active Contributor
0 Kudos

Hello,

As I have already mentioned, this is not recommended to do!!.

If you can help it please refer to Note 1775293. This will be updated shortly with the fix and I repeat what I have already said previously, it is not recommended to create the user in the System DB.

Regards,

Michael

Former Member
0 Kudos

Hi,

I've the same issue, currently we are in a multi-container context.

In the tenant <SID> my user SAPABAP1 exist, but does not exist in my tenant SYSTEMDB

Should i created too the user SAPABAP1 in tenant SYSTEMDB ?

could you more detail your explication ? and do you know, why SAPINST has not created it before to start import ?

Thanks

former_member183326
Active Contributor
0 Kudos

Hello Gael,

There is an issue currently with the SWPM.

There is a fix due very soon for this. If you keep an eye on Note 1775293 for an update.

Creating a user on the SYSTEMDB is not recommended by SAP. This could cause series issues since the sysemdb is running in the nameserver that is shared in the landscape. The systemdb is usually intended for management purposes.

Regards,

Michael

0 Kudos

Thanks Michael,

Could you check the below post as well and let us know if that is related to the bug in SWPM as well:

http://scn.sap.com/message/16291442#16291442

Regards,

Krishna

Answers (1)

Answers (1)

former_member183326
Active Contributor
0 Kudos

Hello Krishna,

Have you tried following Note 2093767?

It seems as if you have entered the wrong password with the user.

Regards,

Michael

0 Kudos

Hello Michael,


Thanks for the response.


Could you let me know which is the user you mean here?

I already checked the SAPAHD user which is mentioned in the error logs i pasted and with the user SAPAHD i was able to login to the DB through the HANA studio and through HDBSQL command line interface and i was able to connect to the DB with the credentials I give.


I am not sure about the SAP note: 2093767 as I am doing an export/import here and my source system is already in SP10 for the SAP_BW Component.


Regards,

Krishna

former_member183326
Active Contributor
0 Kudos

Hello Krishna,

Are you using a multi DB?

Regards.

Michael

0 Kudos

Hello Michael,

Yes the target is a multitenant database.

Regards,

Krishna

former_member183326
Active Contributor
0 Kudos

Hello Krishna,

I am correct saying that you have already opened an incident for this issue?

The issue has been identified. With SPS10 a new message is generated if a wrong password/user is present. This construct is used by migmonctrl to check if multidb is used. SWPM is fixed and will be soon available to customers. It seems themigmonctrl.jar was not able to handle this new message. Therefore migmonctrl.jar has to be adjusted.

Best Regards,

Michael

0 Kudos

Thank You Michael for the information.

Yes it seems to be a bug in the SWPM and we can expect a fix soon.

Regards,

Krishna