While collecting the Sybdiag output, This may fail due to the below Error :
sybdiag -S<SID> -Usapsa -T asecore, keyfile, aseadd
Password:
10000 - Unanticipated Error: An unanticipated error occurred. The message returned was "while trying to invoke the method com.sybase.jdbc4.jdbc.MdaManager.getMetaDataAccessor(java.lang.String, com.sybase.jdbc4.jdbc.ProtocolContext) of a null object loaded from field com.sybase.jdbc4.jdbc.SybConnection._mda of an object loaded from local variable 'this'".
java.lang.NullPointerException: while trying to invoke the method com.sybase.jdbc4.jdbc.MdaManager.getMetaDataAccessor(java.lang.String, com.sybase.jdbc4.jdbc.ProtocolContext) of a null object loaded from field com.sybase.jdbc4.jdbc.SybConnection._mda of an object loaded from local variable 'this'
at com.sybase.jdbc4.jdbc.SybConnection.isSurrogateProcessingDisabledOnServer(SybConnection.java:1044)
at com.sybase.jdbc4.jdbc.SybConnection.determineCharset(SybConnection.java:1254)
at com.sybase.jdbc4.jdbc.SybConnection.init(SybConnection.java:709)
at com.sybase.jdbc4.jdbc.SybConnection.tryLogin(SybConnection.java:625)
at com.sybase.jdbc4.jdbc.SybConnection.handleHAFailover(SybConnection.java:3435)
at com.sybase.jdbc4.jdbc.SybConnection.<init>(SybConnection.java:354)
at com.sybase.jdbc4.jdbc.SybDriver.createConnection(SybDriver.java:680)
at com.sybase.jdbc4.jdbc.SybDriver.connect(SybDriver.java:619)
at com.sybase.jdbc4.jdbc.SybDriver.connect(SybDriver.java:652)
at com.sybase.jdbc4.jdbc.SybDataSource.getConnection(SybDataSource.java:273)
at com.sybase.ase.fdu.sql.ASEConnection.connect(Unknown Source)
at com.sybase.ase.fdu.sql.ASEConnectionManager.reserveConnection(Unknown Source)
at com.sybase.ase.fdu.SybDiag.connectionAuthentication(Unknown Source)
at com.sybase.ase.fdu.SybDiag.run(Unknown Source)
at com.sybase.ase.fdu.SybDiag.main(Unknown Source)
sybdiag has completed with unanticipated errors.
eccr3dev /sybase/TU1> stopsap r3 eccr3dev
stopsap: Command not found.
This issue may be caused due to some errors at ASE server and will be carried till ASE server will be restarted .
Please restart the ASE server to fix this issue and run Sybdiag again.
