About Me

Anjum Ara I am a technology enthusiast, an ardent reader. My latest interest is virtualization. In my free time, I love understanding child nutrition, child holistic development. I bake, read, paint, and do whatever it takes to improve myself every day.

Wednesday, April 15, 2020

FCM Schema Migration

Post FCM schema migration the service won't start due to the Weblogic domain name. This value is stored in a table that needs an update.

Error:
<The logging last resource (LLR) data source accountreconciliation_datasource will not function when it is a participant in a global transaction that spans multiple WebLogic Server instances because remote JDBC support is disabled. LLR will function in single-server configurations.>
####<Apr 14, 2020 12:09:16 PM AST> <Critical> <JTA> <BEC12-ENCX-V357> <FinancialClose0> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000N5rwmI73Z7Qay_EgMG1U_Nqq000002> <1586855356559> <BEA-110482> <A logging last resource failed during initialization. The server cannot boot unless all configured logging last resources (LLRs) initialize. Failing reason:
weblogic.transaction.loggingresource.LoggingResourceException: java.sql.SQLException: JDBC LLR, table verify failed for table 'DEV1_FCM.WL_LLR_FINANCIALCLOSE0', row 'JDBC LLR Domain//Server' record had unexpected value 'Prod_EPMSystem//FinancialClose0' expected 'base_domain//FinancialClose0'*** ONLY the original domain and server that creates an LLR table may access it ***

weblogic.transaction.loggingresource.LoggingResourceException: java.sql.SQLException: JDBC LLR, table verify failed for table 'DEV1_FCM.WL_LLR_FINANCIALCLOSE0', row 'JDBC LLR Domain//Server' record had unexpected value 'Prod_EPMSystem//FinancialClose0' expected 'base_domain//FinancialClose0'*** ONLY the original domain and server that creates an LLR table may access it ***
at weblogic.jdbc.wrapper.JTSLoggableResourceImpl.recoverXARecords(JTSLoggableResourceImpl.java:248)
at weblogic.transaction.internal.ServerTransactionManagerImpl$RegisteredLoggingResourceTransactions.registerLoggingResourceTransactions(ServerTransactionManagerImpl.java:801)
at weblogic.transaction.internal.ServerTransactionManagerImpl.registerLoggingResourceTransactions(ServerTransactionManagerImpl.java:767)
at weblogic.jdbc.common.internal.RmiDataSource.recoverLoggingResourceTransactions(RmiDataSource.java:400)
at weblogic.jdbc.common.internal.DataSourceManager.createAndStartDataSource(DataSourceManager.java:146)
at weblogic.jdbc.common.internal.DataSourceManager.createAndStartDataSource(DataSourceManager.java:101)
at weblogic.jdbc.module.JDBCModule.activate(JDBCModule.java:385)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
at weblogic.application.internal.flow.DeploymentCallbackFlow


Solution:

Go to the <FCMSCHEMA>.WL_LLR_FINANCIALCLOSE0 table and update the value from the incorrect Weblogic Domain name to the correct one. The one from the destination server.Restart the FCM services.

Share:

0 comments: