Restoring autoconfig configurations (How does autoconfig restore.sh script work)



Each time autoconfig is run it creates a folder under [inst_top]/admin/out/. The name of folder is the the date and time of autoconfig run in the mmddhhmi format, This contains resote.sh script with many other files including  context_file.

On running autoconfig it automatically creates a folder with different files for that autoconfig run. After autoconfig run If you find something wrong( like application is not accessible because of last modification) stop the application tier services and go to the relevant autoconfig folder and run restore.sh script to restore previous autoconfig configuration.

The restore.sh will not actually restore the context_file but this will restore all the settings prior to this autoconfig run.(if you had a faulty configuration before, of course restore.sh will restore only those configurations)

After restore.sh is run start up the services(don't run autoconfig), access the application, check the modifications and correct the modifications causing trouble in application. To take effect of new modifications(this must be done using autoconfig editor from OAM) shutdown application services and run autoconfig.

The restore.sh will take you back to the previous configuration (ie the configuration you had when you run autoconfig).


Lets do a test

Change Active Web Port from its value current value 8001to 'bbb'

Save the change when you are asked to change the  dependent parameter say no and click OK on next page. On saving, it will tell you to run autoconfig for new changes to take effect.
Stop the application services and run autoconfig.
Running autoconfig  completes with errors,  lets start the application services and try to access the page.



The page is not appearing because of the wrong port value.

Lets restore the previous autoconfig configuration. Go to the [inst_dopt]/admin/out/ [mmddhhss] folder and run restore.sh. Don't run autoconfig after running restore.sh



Now access the application and go to autoconfig page, click on show history button, click on show differences from current configuration on history page

You can see the current and previous values here, use the restore previous value radio button to restore the correct value


Press ok button
Run autoconfig


Now access the application and go to autoconfig page, click on show history button, click on show differences from current configuration on history page and see.


Comments

Post a Comment

Popular posts from this blog

APP-FND-01436: List of Values cannot find any values for you to choose error from concurrent request program parameter (R12 12.1.3)

Image
APP-FND-01436: List of Values cannot find any values for you to choose error from concurrent request program parameter After upgrading oracle application 11i(11.5.10.2) to R12(12.1.3) running concurrent program request caused this issue When concurrent program is run for a concurrent request after upgrading to R12 12.1.3 the lov, which is attached to a parameter, gives APP-FND-01436: “List of Values cannot find any values for you to choose”. When the same request is run from oracle applications 11i 11.5.10.2 the same value set is working fine. The value set is based on a table. If you go and test the value set query from the value set definition screen it returns complete successful message yet if you go to the parameter of the concurrent request program form where the particular value set is used it gives you the above error. After searching google and oracle support I found metalink note 1400963.1, EBS R12.1: Parameter for Concurrent Request Using Table Based LOV G...
Read more

WEB ADI - issues encountered during initial access

Image
On accessing create document link under Desktop Integrator responsibility browser was showing following error Set BNE UIX Physical Directory profile value to proper directory at site level Location = $COMMON_TOP/html/cabo/  (11i) Location = $COMMON_TOP/webapps/oacore/html/cabo/  (R12) As this was a cloned instance the value of this profile setting was pointing to a wrong location. set as BNE UIX Physical Directory /u03/oracle/prodcomn/html/cabo/ Access to functions are controlled by function security so to access and work with web adi the user should have proper access. You should have access to particular integrator to access and work with it Find out responsibility which is created to work with web adi check the main menu for this responsibility. Modify the responsibility or Menu if default is not fitting to your needs. For instance Desktop Integration Menu has create document, Define Lay out, Define Mapping, Manage Documents, Setup options Note : you...
Read more

Error processing request - Contact your application administrator apex 20.1

Image
After upgrading 11.2.0.4 to 19c with apex 20.1 accessing apex_admin/apex pages was throwing “Error processing request” Contact your application administrator. There were three invalid objects for APEX_200100 WWV_FLOW_SESSION_RAS WWV_FLOW_WIZARD_API WWV_FLOW_DATA_LOADER Tried compiling these objects but compile was completing with PL/SQL: ORA-00942: table or view does not exist To resolve the issue following rant needs to be given then compile (ran both grant and compile as sysdba) grant select on SYS.DBA_XS_DYNAMIC_ROLES to APEX_200100; grant select on SYS.DBA_TAB_IDENTITY_COLS to APEX_200100; alter package APEX_200100.WWV_FLOW_SESSION_RAS compile body; alter package APEX_200100.WWV_FLOW_WIZARD_API compile body; alter package APEX_200100.WWV_FLOW_DATA_LOADER compile body; Returned 0 invalid object for APEX_200100  select * from dba_objects where status = 'INVALID' and owner = 'APEX_200100' ; Now both admin and apex pages ar...
Read more