Resolution:
Description:
============
AppMange utility throws 'Domain Name &ltdomain-name> specified does not exist' while deploying. Please make sure you have typed it correctly' exception whereas Deployment through Administrator GUI works.

Environment:
===========
TIBCO Administrator 5.x.x
TIBCO Runtime Agent 5.x.x
OS : All

Symptoms:
========
1. The Database table: AUAUTHORIZATIONDOMAIN is empty and ADADMINISTRATIONDOMAIN is not empty.
2. Database connection issue.
3. RVD communication issue.
4. EMS communication issue.

Cause:
=====
There is a possibility that the domain is rebuilt using an existing DB schema. The schema owner might have removed the schema objects manually before recreating the domain.

Resolution:
==========
A. For symptom 1 :

1). Stop the domain's Admin, Hawkagent and HMA services on the primary and secondary (if present) admin server(s).

2). Stop the domain's Hawkagent and HMA services on the client machines.

3). If any data present in the AUAUTHORIZATIONDOMAIN table then take a backup.

4). Run the SQL statement to insert a row with the MNAME column value in the AUAUTHORIZATIONDOMAIN table as the value AUTH_&ltdomain-name> and keep the MSCHEMAVERSIONNUMBER and LASTCOMMITNUMBER columns as null.
   INSERT INTO AUAUTHORIZATIONDOMAIN (MNAME) VALUES ('AUTH_&ltdomain-name>');

5). Start the domain's primary Admin service and keep monitoring the AUAUTHORIZATIONDOMAIN table. The Admin service should update the MSCHEMAVERSIONNUMBER column value of the inserted row with a value greater then 0 (probably 2).

6). Start the domain's hawkagent. Log into the admin GUI create a local test user under the Users tab. Check the AUAUTHORIZATIONDOMAIN table, the LASTCOMMITNUMBER column of the inserted row should have been update with a non-zero number.

Try the AppManage utility again, this time it should not throw the 'Domain Name xxxx specified does not exist. Make sure you have typed it correctly'
Restart the domain's hawkagent on the client and secondary servers.

Since, AppManage utility is working, it is recommended to take a -batchExport and re-create the domain and use the -batchDeploy to re-deploy the applications.
You can also import and export any ACLs configured on this domain using ImportDomainSecurity and ExportDomainSecurity.


B. For symptom 2 :
1) Scenario 1 :
a) Check if the Database is up and running, try connecting to it using a a third party tool.
b) Check if the Database driver is getting loaded while running AppManage.
   It can be verified by running AppManage --debug command. You can check if the Database driver is getting loaded or not.
   If the Database driver is not getting loaded then you can add the driver path in the tibco.class.path.extended variable in the AppManage.tra file.

2)Scenario 2 :
a) Check the Administrator.log file to see if you can see the below exception, also restart the administrator and then again verify if you see the below exception in the adminsitrator.log file.

  com.tibco.pof.entity.EntityStoreException: java.sql.SQLException: [tibcosoftwareinc][Oracle JDBC Driver][Oracle]ORA-00955: name is already used by an existing object
        at com.tibco.pof.entitystore.db.DBEntityStore.setCurrentSchemaVersionNumber(DBEntityStore.java:873)
      at com.tibco.pof.authorization.impl.AuthDomainImpl.&ltinit>(AuthDomainImpl.java:83)
      at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
      at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
      at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
      at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
      at com.tibco.pof.entitystore.EntityStoreManager.getReadOnlyEntityDomain(EntityStoreManager.java:357)
      at com.tibco.pof.entitystore.EntityStoreManager.getReadOnlyEntityDomain(EntityStoreManager.java:334)
      at com.tibco.pof.entitystore.EntityStoreManager.getReadOnlyEntityDomain(EntityStoreManager.java:327)
      at com.tibco.pof.entitystore.EntityStoreManager.getReadOnlyEntityDomain(EntityStoreManager.java:320)
      at com.tibco.pof.authorization.AuthorizationDomain.instance(AuthorizationDomain.java:123)
      at com.tibco.pof.authorization.AuthorizationDomain.getMutableDomainByName(AuthorizationDomain.java:153)
      at com.tibco.pof.authorization.AuthorizationDomain.getMutableDomain(AuthorizationDomain.java:128)
      at com.tibco.administrator.AdministratorServlet.i(AdministratorServlet.java:320)
      at com.tibco.administrator.AdministratorServlet.init(AdministratorServlet.java:126)
      at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1139)
      at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:966)
      at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3996)
      at org.apache.catalina.core.StandardContext.start(StandardContext.java:4266)
      at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:760)
      at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:740)
      at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:544)
      at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:634)
      at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:561)
      at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:496)
      at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1203)
      at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:319)
      at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120)
      at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1022)
      at org.apache.catalina.core.StandardHost.start(StandardHost.java:736)
      at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014)
      at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
      at org.apache.catalina.core.StandardService.start(StandardService.java:448)
      at org.apache.catalina.core.StandardServer.start(StandardServer.java:700)
      at org.apache.catalina.startup.Catalina.start(Catalina.java:552)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:597)
      at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295)
      at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:597)
      at com.tibco.administrator.startup.AdminWrapper.&ltinit>(AdminWrapper.java:208)
      at com.tibco.administrator.startup.AdminWrapper.main(AdminWrapper.java:75)
  Caused by: java.sql.SQLException: [tibcosoftwareinc][Oracle JDBC Driver][Oracle]ORA-00955: name is already used by an existing object
  
      at tibcosoftwareinc.jdbc.base.BaseExceptions.createException(Unknown Source)
      at tibcosoftwareinc.jdbc.base.BaseExceptions.getException(Unknown Source)
      at tibcosoftwareinc.jdbc.oracle.OracleImplStatement.execute(Unknown Source)
      at tibcosoftwareinc.jdbc.base.BaseStatement.commonExecute(Unknown Source)
      at tibcosoftwareinc.jdbc.base.BaseStatement.executeUpdateInternal(Unknown Source)
      at tibcosoftwareinc.jdbc.base.BaseStatement.executeUpdate(Unknown Source)
      at com.tibco.pof.entitystore.db.DBEntityStore.setCurrentSchemaVersionNumber(DBEntityStore.java:859)

Please refer the solution : SOL1-DRIG21 -- You will have to restart the DataBase
The above solution might resolve the AppManage related error also.


C) For sympton 3 and 4:

This exception could be seen if there are RV or EMS communication issues.
Verify EMS communication by logging into the EMS server using tibemsadmin
Verify RV communication by running tibrvlisten and tibrvsend.

For the above symptons it is better to open a SR with TIBCO Support as the communication issues could be specific to an environment.

AppMange utility throws 'Domain Name domain-name specified does not exist'. Please make sure you have typed it correctly' exception.