User contributions for Ebasso

23 April 2026

• 12:2712:27, 23 April 2026 diff hist −2‎ IBM Maximo: Migrate MAXDB to RH OpenShift (DB2 Version) ‎ →‎Create MAXDB database
• 12:2712:27, 23 April 2026 diff hist +508‎ IBM Maximo: Migrate MAXDB to RH OpenShift (DB2 Version) ‎ →‎Create MAXDB database
• 12:2412:24, 23 April 2026 diff hist +62‎ IBM Maximo: Migrate MAXDB to RH OpenShift (db2ucmas76-01.yaml) ‎No edit summary current
• 12:2212:22, 23 April 2026 diff hist +3,844‎ IBM Maximo: Migrate MAXDB to RH OpenShift (db2ucmas76-01.yaml) ‎No edit summary
• 12:2012:20, 23 April 2026 diff hist −76‎ IBM Maximo: Migrate MAXDB to RH OpenShift (DB2 Version) ‎ →‎Copy backup file into Container

22 April 2026

• 20:2820:28, 22 April 2026 diff hist −3‎ DB2: Comandos Backup e Restore ‎No edit summary current
• 20:1620:16, 22 April 2026 diff hist +396‎ DB2: Comandos Backup e Restore ‎No edit summary
• 19:5319:53, 22 April 2026 diff hist +2,021‎ N IBM Maximo: Disconnecting MAS Manage from the database for DB Maintenance ‎ Created page with "In the IBM Maximo 7.6 (on‑premises) architecture, this process was straightforward: all Maximo JVMs could be stopped, providing full control over database connectivity during maintenance windows. With the introduction of MAS running on OpenShift, this approach is no longer applicable. The platform automatically manages workload pods and deployments, causing application components to restart automatically. = Procedure = == 1. Stop Maximo Manage Application == First..." current
• 19:4819:48, 22 April 2026 diff hist +1‎ IBM Maximo ‎ →‎Migration to Maximo Application Suite (MAS)
• 19:4819:48, 22 April 2026 diff hist +81‎ IBM Maximo ‎ →‎Migration to Maximo Application Suite (MAS)
• 18:3718:37, 22 April 2026 diff hist −4,586‎ IBM Maximo: Instalação do Maximo Application Suite usando o MAS CLI ‎ Replaced content with "Migrated to this article IBM Maximo: Install Maximo Application Suite using MAS CLI" current Tag: Replaced

20 April 2026

• 21:0521:05, 20 April 2026 diff hist +1,620‎ IBM Maximo: Changing the Database in IBM Maximo Application Suite (MAS) ‎ →‎Update JDBC Settings current
• 20:5020:50, 20 April 2026 diff hist +19‎ IBM Maximo: Changing the Database in IBM Maximo Application Suite (MAS) ‎ →‎System Wide
• 20:4720:47, 20 April 2026 diff hist +823‎ IBM Maximo: Changing the Database in IBM Maximo Application Suite (MAS) ‎ →‎Update JDBC Settings
• 20:4320:43, 20 April 2026 diff hist +262‎ IBM Maximo: Changing the Database in IBM Maximo Application Suite (MAS) ‎ →‎2. Scale Down All Deployments
• 20:2620:26, 20 April 2026 diff hist −2‎ IBM Maximo: Changing the Database in IBM Maximo Application Suite (MAS) ‎ →‎Procedure
• 20:2520:25, 20 April 2026 diff hist +754‎ IBM Maximo: Changing the Database in IBM Maximo Application Suite (MAS) ‎ →‎1. Stop Maximo Manage Application
• 20:2220:22, 20 April 2026 diff hist −26‎ IBM Maximo: Changing the Database in IBM Maximo Application Suite (MAS) ‎ →‎1. Stop Maximo Manage Application
• 20:2120:21, 20 April 2026 diff hist +1,055‎ N IBM Maximo: Changing the Database in IBM Maximo Application Suite (MAS) ‎ Created page with "This guide explains how to change or reconfigure the database connection for IBM Maximo Application Suite (MAS) Manage application. When you need to change the database configuration for MAS Manage, you must stop all MAS Manage deployments, verify database connections are closed, and then reconfigure the JDBC connection settings. = Procedure = == 1. Stop Maximo Manage Application == First, access the Manage maxinst pod and stop the Maximo application: <syntaxhighlig..."

15 April 2026

• 20:5320:53, 15 April 2026 diff hist 0‎ IBM Sterling Connect:Direct : Certificate-Based Authentication Setup using C:D Web Services ‎ →‎1. REST Client Certificate Configuration current

11 April 2026

• 21:4021:40, 11 April 2026 diff hist +19‎ IBM Maximo: Install Maximo Application Suite using MAS CLI ‎ →‎Installing MAS Core via MAS CLI
• 21:3921:39, 11 April 2026 diff hist +9‎ IBM Maximo: Install Maximo Application Suite using MAS CLI ‎ →‎Installing MAS Core via MAS CLI
• 17:5817:58, 11 April 2026 diff hist +166‎ IBM Maximo: Install Maximo Application Suite using MAS CLI ‎ →‎MAS Catalog and versions
• 17:5317:53, 11 April 2026 diff hist −27‎ IBM Maximo: Troubleshooting - Unable to Delete a Project (Namespace) ‎No edit summary current
• 17:5217:52, 11 April 2026 diff hist −3‎ IBM Maximo: Troubleshooting - Unable to Delete a Project (Namespace) ‎No edit summary
• 17:5117:51, 11 April 2026 diff hist −3‎ IBM Maximo: Troubleshooting - Unable to Delete a Project (Namespace) ‎ →‎Immediate Actions to Resolve
• 17:5117:51, 11 April 2026 diff hist +17‎ IBM Maximo: Troubleshooting - Unable to Delete a Project (Namespace) ‎ →‎Resolution
• 17:5017:50, 11 April 2026 diff hist −6‎ IBM Maximo: Troubleshooting - Unable to Delete a Project (Namespace) ‎ →‎Root Cause
• 17:5017:50, 11 April 2026 diff hist +1,290‎ N IBM Maximo: Troubleshooting - Unable to Delete a Project (Namespace) ‎ Created page with "It is not possible to delete a project, even when using force deletion. == Check == Check what resources still exist inside the namespace. Run the following command to export the namespace definition to JSON: oc get namespace $PROJECT_NAME -o json > tmp.json && cat tmp.json Inspect the end of the generated file, especially the '''spec''' section. == Root Cause == In some cases, the deletion is blocked by a controller or operator due to a '''finalizer'''. Example..."
• 17:4517:45, 11 April 2026 diff hist +76‎ IBM Maximo: Install Maximo Application Suite using MAS CLI ‎ →‎Known installation issues
• 17:0817:08, 11 April 2026 diff hist +1‎ IBM Maximo: Install MAS - Image Stream Cannot Be Used as Build Output ‎ →‎= Pod image-registry is not in Ready state current
• 17:0817:08, 11 April 2026 diff hist +694‎ IBM Maximo: Install MAS - Image Stream Cannot Be Used as Build Output ‎ →‎Verification
• 17:0317:03, 11 April 2026 diff hist +128‎ IBM Maximo: Install Maximo Application Suite using MAS CLI ‎No edit summary
• 16:5916:59, 11 April 2026 diff hist −26‎ IBM Maximo: Install Maximo Application Suite using MAS CLI ‎ →‎Installing MAS Core via MAS CLI
• 16:5616:56, 11 April 2026 diff hist −478‎ IBM Maximo: Install MAS - Image Stream Cannot Be Used as Build Output ‎ →‎Common Scenarios
• 10:4510:45, 11 April 2026 diff hist +66‎ IBM Maximo: Install Maximo Application Suite using MAS CLI ‎ →‎Installing MAS Core via MAS CLI
• 10:3810:38, 11 April 2026 diff hist +4,509‎ N IBM Maximo: Install MAS - Image Stream Cannot Be Used as Build Output ‎ Created page with "== Problem Description == When attempting to start a build in OpenShift, you may encounter the following error: <pre> Error starting build: an image stream cannot be used as build output because the integrated container image registry is not configured </pre> This error occurs when a BuildConfig is configured to output to an ImageStream, but OpenShift's integrated container image registry is not available. == Root Cause == The error indicates that: * The BuildConfig..."
• 10:3610:36, 11 April 2026 diff hist +77‎ IBM Maximo: Install Maximo Application Suite using MAS CLI ‎ →‎Known installation issues
• 10:3410:34, 11 April 2026 diff hist −3‎ IBM Maximo: Troubleshooting Maximo Manage Workspace activation ‎ →‎Immediate Actions to Resolve current
• 10:3410:34, 11 April 2026 diff hist −11‎ IBM Maximo: Troubleshooting Maximo Manage Workspace activation ‎No edit summary
• 10:3410:34, 11 April 2026 diff hist −11‎ IBM Maximo: Troubleshooting Maximo Manage Workspace activation ‎No edit summary
• 10:3310:33, 11 April 2026 diff hist −11‎ IBM Maximo: Troubleshooting Maximo Manage Workspace activation ‎No edit summary
• 10:3310:33, 11 April 2026 diff hist +2,508‎ N IBM Maximo: Troubleshooting Maximo Manage Workspace activation ‎ Created page with " Check manageworkspace oc describe manageworkspace -n mas-dev01-manage Result: <nowiki>Name: dev01-demo01 Namespace: mas-dev01-manage Labels: mas.ibm.com/applicationId=manage mas.ibm.com/instanceId=dev01 ...</nowiki> If From the oc describe output, the critical error is in the Status.Conditions section: Type: BuildReady Status: '''False''' Reason: '''Failed''' Message: Build Failed. Type: DeploymentCR Status: True Reason: '..."
• 10:2510:25, 11 April 2026 diff hist +70‎ IBM Maximo: Install Maximo Application Suite using MAS CLI ‎ →‎Known installation issues
• 10:2110:21, 11 April 2026 diff hist +49‎ IBM Maximo: Install Maximo Application Suite using MAS CLI ‎ →‎Installing MAS Core via MAS CLI

10 April 2026

• 20:4720:47, 10 April 2026 diff hist −18‎ IBM Maximo: Install MAS - Known installation issues ‎No edit summary current
• 20:4620:46, 10 April 2026 diff hist +35‎ IBM Maximo: Install MAS - Known installation issues ‎ →‎DRO Failure
• 20:4620:46, 10 April 2026 diff hist +1‎ IBM Maximo: Install MAS - Known installation issues ‎No edit summary
• 20:4520:45, 10 April 2026 diff hist +1‎ IBM Maximo: Install MAS - Known installation issues ‎No edit summary
• 20:4520:45, 10 April 2026 diff hist +1,232‎ N IBM Maximo: Install MAS - Known installation issues ‎ Created page with " = DRO Failure = The DRO (Data Reporter Operator) When the following happens: Wait for the rhm-data-service to be ready. Checking pods <nowiki>oc get pods -n redhat-marketplace NAME READY STATUS RESTARTS AGE ibm-data-reporter-operator-controller-manager-7dbf5f4b75-mxzpj 1/1 Running 0 159m ibm-metrics-operator-controller-manager-588c464b77-7z7bv 1/1 Running 3 (..."