After Packing/Unpacking, Start Script Variables Are Overwritten (Doc ID 2240722.1)

Last updated on AUGUST 22, 2022

Applies to:

Symptoms

After using the pack and unpack utilities, some of the startup scripts in the target installation are changed, and customizations to those scripts are removed. All lines in startup scripts are overwritten.For example, the following files be altered:

• installNodeMgrSvc.cmd
• setDomainEnv.cmd
• setDomainEnv.sh
• setStartupEnv.cmd
• setStartupEnv.sh
• startComponent.cmd
• startComponent.sh
• startManagedWebLogic.cmd
• startManagedWebLogic.sh
• startNodeManager.cmd
• startNodeManager.sh
• startRSDaemon.cmd
• startRSDaemon.sh
• startWebLogic.cmd
• startWebLogic.sh
• stopComponent.cmd
• stopComponent.sh
• stopManagedWebLogic.cmd
• stopManagedWebLogic.sh
• stopNodeManager.cmd
• stopNodeManager.sh
• stopRSDaemon.cmd
• stopRSDaemon.sh
• stopWebLogic.cmd
• stopWebLogic.sh
• uninstallNodeMgrSvc.cmd

In particular, the use of certain variables will result in the values assigned to them being changed. The variables include:

• WL_HOME
• PRODUCT_HOME
• ORACLE_HOME
• MW_HOME
• MW_ORA_HOME
• MW_SCA_HOME
• BAR_WL_HOME
• BEAHOME
• PLATFORMDIR
• JAVA_HOME
• SUN_JAVA_HOME
• BEA_JAVA_HOME
• SAMPLES_HOME
• HOST_NAME
• JAVA_VENDOR
• USERDOMAIN_HOME
• DOMAIN_HOME
• SERVER_NAME
• DOMAIN_NAME
• PRODUCTION_MODE
• WLS_USER
• WLS_PW
• ADMIN_URL

If any of these variables are used in the customization to one of these scripts (or in a custom script), the variable value is changed when the domain is unpacked. For example, consider a custom script "my.sh," with the following contents:

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.