cancel
Showing results for 
Search instead for 
Did you mean: 

Error (38015) : License usage record creation failed for the user infodba

Genius
Genius

After upgrade production DB from 8.3 to 10.1.5 we have problem to connect to one of two upgraded tc databases.

 

Command line login fail! Error code = 70101 (POM_no_class_of_this_name)
POM_class_id_of_class failed with code "POM_no_class_of_this_name" [515155]

 

Error (38015) : License usage record creation failed for the user infodba

 

ERROR -- NoId - 38015 - Error (38015) occurred while performing a licensing operation. Please contact your Teamcenter administrator. - Teamcenter.CoreModelGeneral.tc at d:\workdir\tc1015w1013_win64\src\core\tc\infomanager_itk.cxx(3090)

 

FSC service is working Ok. What can be corrupt? May be in tc_data?

 

Also, we moved upgraded to tc10 tc_database to another server.

2 REPLIES

Re: Error (38015) : License usage record creation failed for the user infodba

Solution Partner Phenom Solution Partner Phenom
Solution Partner Phenom

The DB flavor, Oracle or MSSQL, determines which files need to be modified in TC_DATA when moving the DB instance to a different server. MSSQL is simple and you only need to modify tc_profilevars.bat. Oracle also requires modifying tnsnames.ora.

Modify:

  • Rename the log dir: log_<old_db_server>_<db_name> to log_<new_db_server>_<db_name>
  • Rename pom scehma: pom_schema_<old_db_server>_<db_name> to pom_schema_<new_db_server>_<db_name>
  • Modify tc_profilevars.bat
  • Modify tnsnames.ora (Oracle only)

Validate that your connection to the database is good by running:

  • install -ayt (should see "site is already installed"; anything is a failure to connect)

Don't forget to:

  • Regen the pom schema
  • Clearlocks assert_all_dead

Randy Ellsworth, Teamcenter Architect, Applied CAx, LLC
NX 11.0.1.mp01 | SW 2016 | TcUA 11.2.3
Evaluating:AW 3.2

Re: Error (38015) : License usage record creation failed for the user infodba

Genius
Genius

Problem was in corrupt TC_ROOT. We replaced corrupt TC_ROOT with correct TC_ROOT from backup and this error went away