Frequent errors During ATG installation

1. Cim tool throwing error 255 saying start sqlrepository unexpected/ java unexpected (or) Error While importing Data using CIM tool.

If You see "\Java\jdk1.6.0_27\bin\java was unexpected at this time" in CIM log then go to ATG_HOME\bin\dasEnv.bat and change java home path.

and if you see "& was unexpected at this time" make sure that ojdbc is set in the class path before executing CIM.bat

2. ATG CRS giving javax.servlet.ServletException: Can't find component named: /atg/registry/Slots/HomeTheme

If you are facing this error there might be two possibilities to rectify it.

2.1 Go with Full Deployment of CRS it will solve this problem

2.2 Even after Full Deployment If you are getting the same exception, Data imports are not Proper. Drop the Schemas and reImport Data.

3. ATG Publishing/Production Server throwing  Authentication for user weblogic denied Saying:

 <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user weblogic denied

weblogic.security.SecurityInitializationException: Authentication for user weblogic denied

Follow the following steps:

1. Just edit boot.properties file, use plain text username and password instead of encrypted like
Username: weblogic
password: Weblogic1
2: remove the ManagedServerDir/data/ldap directory completely.
3: Always keep backup of files before removing it.
4: Now try to start the server from the command prompt and provide the username/password used to login to the Admin Console.

4. Error While Configuring Data Source in WebLogic

ORA-28009: connection as SYS should be as SYSDBA or SYSOPER <br/>oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:440)<br/>oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) - Google Search

Make Sure You Gave the Username and Password of the Schemas for Configuring the DataSources Instead of dataBase Password.

if you want to bypass  SYSDBA

1. Log in to sqlplus as sys

 command: conn / as sysdba

2. Check for parameter named O7_DICTIONARY_ACCESSIBILITY

Command: show parameter O7_DICTIONARY_ACCESSIBILITY

3. Change this parameter using

Command: alter system set O7_dictionary_accessibility=TRUE scope=spfile;
 
4. Restart Server.
 

Kindly post a comment if you are facing any problems other than this. It will be Addressed Soon.