This looks as it is maybe a simple permissions issue with your maximo user for SQL, a password issue for the DB user, or an issue with your jdbc connection string. It clearly can't connect to the DB, so I would double check all of those values and make sure that you input the right ones. Your database update never kicks off, which is why you don't see any database update logs in in your Maxinst pod.
Your configuration is sound and the way you have it set up should work. 2019 is the minimum version to deploy MAS on, so you're good there too. That little green check box that appears on the UI does not mean you're connected to the database. It's kind of misleading.
Original Message:
Sent: Fri December 13, 2024 12:16 PM
From: karthik krishnamurthy
Subject: MAS-Manage with SQL database issue
Hi Bret,
yes, as you mentioned we have the same Schmea(dbo) , TableSpace(PRIMARY), IndexSpace(PRIMARY) configuration in our SQL database,
some additional details for your reference here,
while deploying Manage under Application Scope, we got some errors on 3 phases. please refer the below image
database information are
please let me know if DB upgrade is required.
as per IBM documentation it needs to be 2019 ?
we have database name as 8 characters size, is there any issue on DB name?
Thanks,
Karthik Krishnamurthy
------------------------------
karthik krishnamurthy
Original Message:
Sent: Fri December 13, 2024 09:54 AM
From: Brett Coleman
Subject: MAS-Manage with SQL database issue
Hi Karthik,
This looks vaguely familiar to me. It's been a while since I stood up our instance of MAS, so it's slowly coming back to me. If @Bradley Downing's solution doesn't work for you, I would double check the values that you provided for schema, index space and table spaces for the DB. For SQL server the values are dbo for the schema, and PRIMARY for the index and table spaces. I was running into issues with the DB upgrading when I was first trying to deploy manage because I was trying to use MAXIMO for the schema.
It should look like this:
------------------------------
Brett Coleman
Original Message:
Sent: Fri December 13, 2024 04:32 AM
From: karthik krishnamurthy
Subject: MAS-Manage with SQL database issue
Hi Brett,
Thank you for the response.
as you said yes, maxinst pod is ready inside OpenShift portal
below text are from Logs on the same maxinst pod.
copppropertyfileThu Dec 12 16:18:54 UTC 2024 INFO: use the non-fips xml configuration ...generateKeyStore...-- Maximo Process Automation Engine 9.0.0.0 Build 20240924-0648 DB Build V9000-127,Maximo Integration Framework 9.0.0 Build 20240924-0648 DB Build V9000-20 HFDB Build HF9000-04,IBM Maximo Mobile 9.0.0 Build 20240924-0935 DB Build V9000-74 HFDB Build HF9000-07,Maximo Application Framework 9.0.0 Build 20240924-1320 DB Build V7600-36,Manage Foundation 9.0.0 Build 20240924-0648 DB Build V9000-37 HFDB Build HF9000-02,Maximo Manage 9.0.0 Build 20240924-0648 DB Build V9000-01 HFDB Build HF9000-8-- ************************Start undo extension.... -- Type: field For object: MAXIFACEOUT,RETAINMBOS Product class : psdi.iface.app.publish.FldRetainMbos Extend from: null-- Type: field For object: MAXIFACEOUT,RETAINMBOS Product class : psdi.iface.app.publish.FldRetainMbos Super class: psdi.mbo.MAXTableDomain-- Start processing first class: psdi.iface.app.publish.FldRetainMbos-- Extension updating class file: InputFile psdi.iface.app.publish.FldRetainMbos extending from psdi.mbo.MAXTableDomain , same super-- Extension updating class file: InputFile psdi.iface.app.publish.FldRetainMbos extending from psdi.mbo.MAXTableDomain-- Instruction class name : psdi.mbo.MAXTableDomain Signature: (Lpsdi/mbo/MboValue;)V Input class name: psdi.iface.app.publish.FldRetainMbos-- Extension update: successful-- Type: field For object: APILINKEDOBJECT,PARENT Product class : com.ibm.tivoli.maximo.oslc.provider.app.FldParent Extend from: null-- Type: field For object: APILINKEDOBJECT,PARENT Product class : com.ibm.tivoli.maximo.oslc.provider.app.FldParent Super class: psdi.mbo.MAXTableDomain-- Start processing first class: com.ibm.tivoli.maximo.oslc.provider.app.FldParent-- Extension updating class file: InputFile com.ibm.tivoli.maximo.oslc.provider.app.FldParent extending from psdi.mbo.MAXTableDomain , same super-- Extension updating class file: InputFile com.ibm.tivoli.maximo.oslc.provider.app.FldParent extending from psdi.mbo.MAXTableDomain-- Instruction class name : psdi.mbo.MAXTableDomain Signature: (Lpsdi/mbo/MboValue;)V Input class name: com.ibm.tivoli.maximo.oslc.provider.app.FldParent-- Extension update: successful-- Type: field For object: MSGHUBPROVIDER,PROVIDERTYPE Product class : com.ibm.tivoli.maximo.messagehub.FldProviderType Extend from: null-- Type: field For object: MSGHUBPROVIDER,PROVIDERTYPE Product class : com.ibm.tivoli.maximo.messagehub.FldProviderType Super class: psdi.mbo.MAXTableDomain-- Start processing first class: com.ibm.tivoli.maximo.messagehub.FldProviderType-- Extension updating class file: InputFile com.ibm.tivoli.maximo.messagehub.FldProviderType extending from psdi.mbo.MAXTableDomain , same super-- Extension updating class file: InputFile com.ibm.tivoli.maximo.messagehub.FldProviderType extending from psdi.mbo.MAXTableDomain-- Instruction class name : psdi.mbo.MAXTableDomain Signature: (Lpsdi/mbo/MboValue;)V Input class name: com.ibm.tivoli.maximo.messagehub.FldProviderType-- Extension update: successful-- Type: field For object: MAXIFACEOUT,MESSAGETYPE Product class : psdi.iface.app.common.FldMessageType Extend from: null-- Type: field For object: MAXIFACEOUT,MESSAGETYPE Product class : psdi.iface.app.common.FldMessageType Super class: psdi.mbo.ALNDomain-- Start processing first class: psdi.iface.app.common.FldMessageType-- Extension updating class file: InputFile psdi.iface.app.common.FldMessageType extending from psdi.mbo.ALNDomain , same super-- Extension updating class file: InputFile psdi.iface.app.common.FldMessageType extending from psdi.mbo.ALNDomain-- Instruction class name : psdi.mbo.ALNDomain Signature: (Lpsdi/mbo/MboValue;)V Input class name: psdi.iface.app.common.FldMessageType-- Extension update: successful-- Type: field For object: MAXQUEUE,ISSEQUENTIAL Product class : psdi.iface.app.extsystem.FldIsSequentialQueue Extend from: null-- Type: field For object: MAXQUEUE,ISSEQUENTIAL Product class : psdi.iface.app.extsystem.FldIsSequentialQueue Super class: psdi.mbo.MboValueAdapter-- Start processing first class: psdi.iface.app.extsystem.FldIsSequentialQueue-- Extension updating class file: InputFile psdi.iface.app.extsystem.FldIsSequentialQueue extending from psdi.mbo.MboValueAdapter , same super-- Extension updating class file: InputFile psdi.iface.app.extsystem.FldIsSequentialQueue extending from psdi.mbo.MboValueAdapter-- Instruction class name : psdi.mbo.MboValueAdapter Signature: (Lpsdi/mbo/MboValue;)V Input class name: psdi.iface.app.extsystem.FldIsSequentialQueue-- Extension update: successful-- Type: field For object: APILINKEDOBJECT,RELATION Product class : com.ibm.tivoli.maximo.oslc.provider.app.FldRelation Extend from: null-- Type: field For object: APILINKEDOBJECT,RELATION Product class : com.ibm.tivoli.maximo.oslc.provider.app.FldRelation Super class: psdi.mbo.MAXTableDomain-- Start processing first class: com.ibm.tivoli.maximo.oslc.provider.app.FldRelation-- Extension updating class file: InputFile com.ibm.tivoli.maximo.oslc.provider.app.FldRelation extending from psdi.mbo.MAXTableDomain , same super-- Extension updating class file: InputFile com.ibm.tivoli.maximo.oslc.provider.app.FldRelation extending from psdi.mbo.MAXTableDomain-- Instruction class name : psdi.mbo.MAXTableDomain Signature: (Lpsdi/mbo/MboValue;)V Input class name: com.ibm.tivoli.maximo.oslc.provider.app.FldRelation-- Extension update: successful-- Type: service For object: MIC Product class : psdi.iface.mic.EntMicService Extend from: null-- Type: service For object: MIC Product class : psdi.iface.mic.EntMicService Super class: psdi.iface.mic.MicService-- Start processing first class: psdi.iface.mic.EntMicService-- Extension updating class file: InputFile psdi.iface.mic.EntMicService extending from psdi.iface.mic.MicService , same super-- Extension updating class file: InputFile psdi.iface.mic.EntMicService extending from psdi.iface.mic.MicService-- Instruction class name : psdi.iface.mic.MicService Signature: ()V Input class name: psdi.iface.mic.EntMicService-- Instruction class name : psdi.iface.mic.MicService Signature: (Lpsdi/server/MXServer;)V Input class name: psdi.iface.mic.EntMicService-- Extension update: successful-- ***************************End undo extension....-- Product: Maximo Integration Framework extension update starts...-- Product: Maximo Integration Framework extension update complete: SUCCESSFUL-- Product: IBM Maximo EAM to Health Integration extension update starts...-- Product: Budget Application extension update starts...-- Product: Dynamic Job Plan extension update starts...-- Product: Maximo Application Framework extension update starts...-- Product: Maximo Manage extension update starts...-- Product: Manage Foundation extension update starts...-- Product: IBM Maximo Mobile extension update starts...-- Product: IBM Maximo Asset Management Work Centers extension update starts...-- Product: IBM Maximo Asset Management Scheduler extension update starts...-- Product: IBM Maximo Linear Management extension update starts...Launching default (WebSphere Application Server 24.0.0.6/wlp-1.0.90.cl240620240603-2001) on Eclipse OpenJ9 VM, version 11.0.22+7 (en_US)[AUDIT ] CWWKE0001I: The server default has been launched.[ERROR ] CWWKF0042E: A feature definition cannot be found for the wasjmsclient-2.0 feature. Try running the command, bin/installUtility install wasjmsclient-2.0, to install the feature. Alternatively, you can run the command, bin/installUtility install default, to install all features that are referenced by this configuration.[AUDIT ] CWWKZ0058I: Monitoring dropins for applications.[WARNING ] CWOWB1009W: Implicit bean archives are disabled.[AUDIT ] CWPKI0820A: The default keystore has been created using the 'keystore_password' environment variable.[AUDIT ] CWWKS4104A: LTPA keys created in 2.368 seconds. LTPA key file: /opt/was/liberty/wlp/usr/servers/default/resources/security/ltpa.keys[AUDIT ] CWPKI0803A: SSL certificate created in 4.790 seconds. SSL key file: /opt/was/liberty/wlp/usr/servers/default/resources/security/key.p12[AUDIT ] CWWKT0016I: Web application available (default_host):
http://(------------------):9080/toolsapi/
[AUDIT ] CWWKZ0001I: Application toolsapi started in 10.215 seconds.BMXAA6472I toolsapi ready for client connections[AUDIT ] CWWKF0012I: The server installed the following features: [appSecurity-2.0, appSecurity-3.0, beanValidation-2.0, cdi-2.0, distributedMap-1.0, ejbLite-3.2, el-3.0, jaspic-1.1, javaMail-1.6, jaxrs-2.1, jaxrsClient-2.1, jdbc-4.2, jndi-1.0, jpa-2.2, jpaContainer-2.2, jsf-2.3, jsonb-1.0, jsonp-1.1, jsp-2.3, managedBeans-1.0, monitor-1.0, servlet-4.0, ssl-1.0, webProfile-8.0, websocket-1.1].[AUDIT ] CWWKF0011I: The default server is ready to run a smarter planet. The default server started in 27.948 seconds.
Please check and let me know if you found anything to do
Thanks,
Karthik Krishnamurthy
------------------------------
karthik krishnamurthy
Original Message:
Sent: Thu December 12, 2024 02:12 PM
From: Brett Coleman
Subject: MAS-Manage with SQL database issue
Hi Karthik,
The majority of the Manage DB setup and upgrades happen inside of the Maxinst pod. It lives within the Manage project in your cluster.
Has that pod created? If it has, I would start by checking the logs there and see what kind of errors it i throwing.
That's your best starting place. Unfortunately, installing through the UI doesn't really give too much constructive feedback in regards to troubleshooting. If I had to guess, it's probably just a small configuration issue.
------------------------------
Brett Coleman
Original Message:
Sent: Thu December 12, 2024 12:52 PM
From: karthik krishnamurthy
Subject: MAS-Manage with SQL database issue
Hi,
I am trying to installing MAS 9.0.x and configuring Existing MS SQL database on ARO cluster.
steps followed in the below order
- Created a SQL database instance and stored in Azure VM.
- ARO clusters created in Azure
- MAS 9.0.x installed using Ansible approach
- MAS installed on ARO
- on MAS Adminstration page using the Database Configuration setup to configure the existing SQL DB URL
- But it keep on Loading on Activating page.
In this stage i am expecting any error related to DB version, etc. But there is no issue on Activating process.
Any Help to configure existing SQL Database would be appreciated
Thanks,
Karthik Krishnamurthy
------------------------------
karthik krishnamurthy
------------------------------