Support Article
Invalid object name error reported during PRPC upgrade process
SA-657
Summary
In PRPC upgrade process from PRPC 6.1 SP2 to PRPC 7.1 ML6, the migrate.bat script used to upgrade the schema has exited with SQLServerException apparently while looking for an object named 'dbo.EventsChangeLog'.
Error Messages
[java] com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'dbo.EventsChangeLog'.
[java] at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:156)
[java] at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1373)
[java] at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(SQLServerStatement.java:702)
[java] at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(SQLServerStatement.java:600)
[java] at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:4003)
[java] at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1550)
[java] at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:160)
[java] at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:133)
[java] at com.microsoft.sqlserver.jdbc.SQLServerStatement.execute(SQLServerStatement.java:573)
[java] at com.pega.pegarules.install.SQLLoader.main(SQLLoader.java:298)
[java] Aug 24, 2014 8:03:01 PM com.pega.pegarules.install.SQLLoader writeMessage
[java] INFO:
[java]
[java]
[java] Encountered a SQL Exception, clean schema before running again.
Steps to Reproduce
1. To reproduce this error, user has to run the migrate.bat script on the database server with the appropriate privileges.
2. Create custom DDL trigger that copies the changes in the database and do not update this custom trigger to point to new schema.
3. Run the migrate.bat script, that will encounter “Invalid object name” error since this custom trigger was not be present in the new schema.
Root Cause
Trigger causing the error 'dbo.EventsChangeLog' was custom DDL trigger that populates the LogChangeEvents table. User has copied the objects in the database to a new schema but did not update the DDL trigger. This has caused all create table statements failing in their environment.
Resolution
Suggested user to modify LogChangeEvents custom trigger to reference the correct schema qualified EventsChangeLog table and then run the PRPC upgrade process.
Published April 1, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.