I'm try upgrade CA SDM 12.6 to CA SDM 14.1. In our environment is just one Primary Server (Win2k8 64bits) with CA SDM 12.6 and a remote Database Server (Solaris) with Oracle 11g (MDB).
So when we start the run the migration process as Administrator. , have following error:
2015/11/17 17.01.15.481 DEBUG [DeployThread: Migrando o CA Service Desk Manager] [DatabasePersister] Update to al_cdb_componentinstallstate successful
2015/11/17 17.01.15.481 INFO [DeployThread: Migrando o CA Service Desk Manager] [DeployThread] Task 'task.migrate_sdm' status saved to DB ....
2015/11/17 17.01.15.481 INFO [DeployThread: Migrando o CA Service Desk Manager] [Task] Running: Migrando o CA Service Desk Manager
2015/11/17 17.01.15.481 DEBUG [DeployThread: Migrando o CA Service Desk Manager] [ConfigUIUtils] GENLEVEL.12611053G900.prev_version value : r12_6
2015/11/17 17.01.15.481 DEBUG [DeployThread: Migrando o CA Service Desk Manager] [MigrateSDM] migrateCMD 0 : pdm_perl
2015/11/17 17.01.15.481 DEBUG [DeployThread: Migrando o CA Service Desk Manager] [MigrateSDM] migrateCMD 1 : migrate_to_r14_1.pl
2015/11/17 17.01.15.497 DEBUG [DeployThread: Migrando o CA Service Desk Manager] [ProcessUtilities] Executing command: pdm_perl.exe migrate_to_r14_1.pl
2015/11/17 17.01.15.528 INFO [DeployThread: Migrando o CA Service Desk Manager] [ActiveProcessHolder] Windows Process ID (PID): 5488
2015/11/17 17.01.15.528 INFO [DeployThread: Migrando o CA Service Desk Manager] [ActiveProcessHolder] Start Monitor. Process ID (PID): 5488
2015/11/17 17.01.15.699 DEBUG [stderr( C:\PROGRA~2\CA\SERVIC~1\bin\pdm_perl.exe):Thread-30] [MigrateSDM] Can't open perl script "migrate_to_r14_1.pl": No such file or directory
2015/11/17 17.01.15.965 INFO [DeployThread: Migrando o CA Service Desk Manager] [ActiveProcessHolder] Exit Monitor. Process ID (PID): 5488
2015/11/17 17.01.15.965 INFO [DeployThread: Migrando o CA Service Desk Manager] [ProcessUtilities] Process C:\PROGRA~2\CA\SERVIC~1\bin\pdm_perl.exe completed with exit code 2
2015/11/17 17.01.15.965 DEBUG [DeployThread: Migrando o CA Service Desk Manager] [ProgressPage] ProgressPage - Task Changed Migrando o CA Service Desk Manager
Where the "pdm_perl" don't find the file "migrate_to_r14_1.pl",
Here show we trying (and retryng) upgrade, in the step 4 (Migration CA Service Desk manager) the error above occurs:
Someone had this error? any suggestion?
Does the program migrate_to_r14_1.pl show up in the directory: C:\PROGRA~2\CA\SERVIC~1\bin ?
Secondly, open a command prompt and change directory to c:\
Type dir /x
I'm trying to see if progra~2 really is a shortname for program files (x86) or not.
The file there is no in the directory: C:\PROGRA~2\CA\SERVIC~1\bin
The PROGRA~2 = Program Files (x86).
In the \bin, I have only files concerning migration to 12.6 when it was made.
Would you be able give me some background on how the upgrade was attempted?
It almost seems like when you tried the 14.1 installer, it detected that you had 14.1 software and did not lay down the 14.1 software.
I would suggest you raise a support case for this so that we can dig into the logs a bit and understand where the failure is
I already have a support case opened in the support CA, but they are taking time to reply my case, so I am search the solution. This moment my DBA is doing dump (import/export) again of the Database Production for my Database Test for that we start again the migration test.
There's no way have had the 14.1 software. In the log show the version is 12.6. The steps for our migration, we just clone the Production environment (App and DB), and of course, changed the servers names, IPs, change listener name and etc, to finish and tests, ran pdm_configure and started SDM 12.6 cloned , the application did work normally.
If 12.6 was already up and running properly, then 14.1 should detect 12.6 and set upgrade detected flag to 1.
14.1, if it detects upgrade, here's what it should do:
1) lay down 14.1 common tables
2) lay down 14.1 sofware
3) upgrade MDB
4) run SDM data migration
5) run pdm_configure
6) do any post integrations
From the looks of it, where it might have given grief is with #2 above.
Are you sure there's no fresh 14.1 install anywhere in in this whole architecture ?
Hi, today we will start the upgrade test again, I'll inform you after test.
Raghu , my architecture is following:
APP: Win2008k 64bits, CA SDM 12.6.
DB: Solaris, DB Oracle 11g, MDB 1.5
Another Products: Win2008k 64bits, BOXI 3.1
We have ITPAM, but not integrated with CA SDM and nor in use.
So, in my process I checked the log and saw the flag setted to 1, the Version 12.6 was detected, common table was created with success and error occurred when it search the file "migrate_to_r14_1.pl" and not found (NX_ROOT\bin).
In my pictured below, I'll translation for you what did OK, and where the failure occurs:
1 - Configuring the common table of the CA SDM (OK)
2 - Upgrading the CA SDM (OK)
3 - Installing the schema of Remote Database CA SDM (OK)
4 - Migrating CA SDM (Error / Fail)
5 - Configuring CA SDM (Waiting procces above)
6 - Integrating Products (Waiting procces above)
Another doubt, in this version 14.1, I need or not install MDB in Remote database (Solaris / Oracle 11g) before all process? My MDB is Version 1.5, according matrix MDB 1.5 is compatible with CA SDM 14.1.
Thank you for the detailed update.
I think - Upgrading the CA SDM (OK). This step somehow did not work properly. Or else we should see the 14.1 binaries in nxroot/bin
Remote oracle should be fine. We have the ability to upgrade remote DB using the main installer that you ran.
Hi Raghu, thank you for your help.
Now, using the d:\products\sdm\setup.exe, the file " "migrate_to_r14_1.pl" was created, but the screen and steps is different relative to one another d:\setup.exe, We have error of the MDB, I believe that will need install MDB before install SDM, I will try this again.
There are two error:
Wed Nov 25 11:49:53 2015: Migration Task Completed: verify_tables
Wed Nov 25 11:49:53 2015: >> Running Cmd (pdm_sql "UPDATE usp_servers SET server_id=0 WHERE server_id is NULL" 2>&1 |)
Wed Nov 25 11:49:55 2015: >> UPDATE usp_servers SET server_id=0 WHERE server_id is NULL
Wed Nov 25 11:49:55 2015: >> *
Wed Nov 25 11:49:55 2015: >> ERRO na linha 1: (Error in line 1)
Wed Nov 25 11:49:55 2015: >> ORA-00904: "SERVER_ID": identificador inv⭩do (invalid identifier)
11/25 11:49:03.762 INFO ? ? 11-25,11:49:03 Usage: Invalid argument "<DBPASSWORD>"
11/25 11:49:03.902 INFO ? ? 11-25,11:49:03 Setupmdb exit /B return code=90
11/25 11:49:04.183 INFO ? ? Process "C:\PROGRA~2\CA\SERVIC~1\add-ons\mdb\oracle\setupmdb.bat" completed with exit code 90
11/25 11:49:04.183 ERROR ? ? Setup MDB returns code 90
11/25 11:49:04.183 ERROR ? ? MDB RC : 90
11/25 11:49:04.183 ERROR ? ? MDB Error: Erro inesperado. Verifique os logs em C:\PROGRA~2\CA\SERVIC~1\temp\mdb_oracle.
11/25 11:49:04.183 ERROR ? ? Check mdb logs at C:\PROGRA~2\CA\SERVIC~1\temp\mdb_oracle.
11/25 11:49:04.183 ERROR InstallOracleMdbTask.java 177 SetupMDB returns code 90
My password have "#", maybe is not support in password?
Before the migration, in the table USP_SERVER, there is nothing: (Is conventional configuration).
Hi, open the disk of instalation and open the setup.exe in this location D:products\SDM. Try.
Thank you, I will try this, now I have the option to install MDB for SDM 14.1, throught d:\setup.exe don't show this options.
After test in my environment and inform you.
you are welcome.