IBM Maximo - Convert DB2 to Oracle

Referring to Unlcvt utility in Maximo 7.6

IBM has deprecated its tool UNLCVT for Maximo 7.6

You can download the tool from here

Extract the content, then copy unlcvt.bat and unlcvt.sh to 

MAXIMO-SMP\maximo\tools\maximo\internal

Extract Configure zip file and copy the Unlcvt.class to 

MAXIMO-SMP\maximo\applications\maximo\businessobjects\classes\psdi\configure

Please follow these steps to convert your database

0. Stop the existing Maximo server on X System (current)

1. Create MAXDEMO.ORA file from the existing DB2 database, using this command under X System: C:\ibm\SMP\maximo\tools\maximo\internal\Unlcvt.bat -oMAXDEMO -x1

2. Install middleware on the Y system designated for the future MAXIMO Oracle system.

3. Install oracle 10g, create maxdata tablespace, maximo user.

4. On Y System, Install Maximo Asset Management with CUSTOM settings, choose to AUTOMATE WEBSPHERE

5. On Y System, Stop WAS Maximo Server after installation completes

6. C:\ibm\SMP\maximo\tools\maximo\en .... Rename maxdemo.ora into maxdemo_original.ora

7. Copy the MAXDEMO.ora file created in step 2 to Y SYSTEM, C:\ibm\SMP\maximo\tools\maximo\en

7.1 optional in my case I edited the maxdemo.ora file created in step 2 (has more than 3700000 lines) and I eliminated all the statements like 'insert into report%' 

You can use UltraEdit for the edition of big files more than 2Gb

8. Move the existing log files from C:\ibm\SMP\maximo\tools\maximo\log into C:\ibm\SMP\maximo\tools\maximo\log\1

9. From command prompt, run the MAXINST command under the Y System 'C:\ibm\SMP\maximo\tools\maximo>maxinst -e -sMAXDATA -tMAXDATA'

10. Check doclinks.properties and other customization, edit them, rebuild, redeploy, restart WAS MAXIMO SERVER.

IBM Maximo DB2 Database - How to perform an online backup / restore

When your DB2 database is running in an ONLINE mode. the system starts producing archive logs.

In order to restore this database to another database, your original backup should contain these log files to roll forward the database to end of logs and complete.

Backup :

Issue Following Command :

	-- Connect to the database console
	db2cmd
	-- Set the current instance
	set DB2INSTANCE=DB2
	-- Issue backup command
	backup db maxdb76 online TO "C:\Command" COMPRESS INCLUDE LOGS

view raw backupdb2online.sql hosted with ❤ by GitHub

Restore :

Create a folder called Command under your system root (C:\Command)

Copy the database backup file to this folder

Open CMD and change directory to C:\Command by issuing cd C:\Command

Now follow the below script :

	-- Connect to the database console
	db2cmd
	-- Set the current instance
	set DB2INSTANCE=DB2
	--Make sure all connections are closed (Maximo stopped)
	--Stop the database
	db2stop force
	--Start the database
	db2start
	-- Issue this command to generate the db.txt script
	-- 20161114160751 is the rowstamp of your database, take it from the database backup name
	db2 restore db maxdb76 from C:\Command taken at 20161114160751 redirect generate script db.txt
	-- Open db.txt for edit
	-- Change LOGTARGET by specifying the folder where to extract the log from the backup
	-- unckech and put the correct system root SET STOGROUP PATHS FOR IBMSTOGROUP ON 'C:'
	-- Specify the target database in INTO parameter
	-- Save the file then issue the command
	db2 -tvf db.txt
	-- After restore completed , now run the rollforward the database
	-- c:\LOG specified in log target of the command db2 restore
	db2 rollforward db maxdev to end of logs and complete overflow log path ("c:\LOG")
	-- Now try to connect to the database, it should work
	db2 connect to maxdb76

view raw restoreonlinedb2.sql hosted with ❤ by GitHub

IBM Maximo DB2 Database - How to update database logs

After installation of the database, the system will maintain all logs under the database instance folder (Usuallly it is C:\DB2). 

After installing more than one database it is recommended to group all these logs in one folder per database.

Follow below steps to organize your database log.

	-- Connect to the database console
	db2cmd
	-- Set the current instance
	set DB2INSTANCE=DB2
	-- Connect to the database
	db2 connect to maxdb76
	-- Create folder to host all logs example here (C:\LOG\LOG_MAXDB76)
	-- Create 5 folder for all log types (logarchmeth1 - logarchmeth2 - failarchpath - logpath - mirrorlogpath)
	-- 8192 bytes is the size of the log file
	-- 20 is the number of primary log files (pre allocated)
	-- 100 is the number of secondary log files (allocated once is needed from the database)
	UPDATE DATABASE CONFIGURATION USING logarchmeth1 "DISK:C:\DB2\LOG\LOG_MAXDB76\logarchmeth1"
	logarchmeth2 "DISK:C:\DB2\LOG\LOG_MAXDB76\logarchmeth2" failarchpath "C:\DB2\LOG\LOG_MAXDB76\failarchpath"
	newlogpath "C:\DB2\LOG\LOG_MAXDB76\logpath" mirrorlogpath "C:\DB2\LOG\LOG_MAXDB76\mirrorlogpath"
	logprimary 20 logsecond 100 logfilsiz 8192 LOGINDEXBUILD OFF
	-- Restart the database
	db2stop force
	db2start

view raw updatedb2log.sql hosted with ❤ by GitHub