[#QA-66] The autoupgrade utility looks for non-existent source service name on target server in the Hot-Cloning method

Questions & Answers

The autoupgrade utility looks for non-existent source service name on target server in the Hot-Cloning method

Created: 06/Feb/25 02:12 PM Updated: 06/Feb/25 09:53 PM

Fix Version/s:

None

File Attachments:

None

Image Attachments:

1. OracleServiceRepo.png
(62 kb)

Product Version:	24.8.241119
Operating System:	Windows
Host Name:	.
Database Name:	.

Description

« Hide

PROBLEM:

Even though source database service name does not look required on target server in the Hot-Cloning (Unplug-Plug Relocate) method, the autoupgrade utility still looks for non-existent source service name on target server. This problem occurs when source database is a CDB or not.

DATABASES:

Source database version: 12.2.0.1 (EE)
Target database version: 19.25 (EE)

CONFIGURATION:

global.autoupg_log_dir=C:\oracle\app\Ora-Admin\cfgtoollogs\autoupgrade
upg1.manage_network_files=SKIP
upg1.sid=REPO
upg1.source_home=C:\oracle\product\12.2.0\dbhome_1
upg1.target_cdb=PRODCDB
upg1.target_home=C:\oracle\app\Ora-Admin\product\19.0.0\dbhome_1
upg1.target_pdb_copy_option.REPO=file_name_convert=('C:\ORACLE\ORADATA\', 'D:\ORACLE\ORADATA\PRODCDB\')
upg1.source_dblink.REPO=repo_link 600
upg1.start_time=30/01/2025 14:00:00

ERROR MESSAGE:

DOS> %ORACLE_HOME%\jdk\bin\java -jar %ORACLE_HOME%\rdbms\admin\autoupgrade.jar -config REPO-autopgrade_config.txt -mode deploy
AutoUpgrade 24.8.241119 launched with default internal options
Processing config file ...

There were conditions found preventing AutoUpgrade from successfully running

*Windows Service Availability
Windows service, OracleServiceREPO, does not exist


DOS>

All

Comments

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

ubTools Support - 06/Feb/25 02:42 PM - edited

WORKAROUND:

Create a dummy Windows service named for source database SID.

DOS> oradim -new -sid REPO
Instance created.

DOS>

Disable created service to be sure the autoupgrade utility cannot call it.

The OracleVssWriter services are also disabled since They are not needed in the case.

Run the autoupgrade utility again.
After the autoupgrade utility completes successfully, deleting created service is recommended.

DOS> oradim -delete -sid REPO
Unable to stop service, OS Error = 1062
Instance deleted.

DOS>