Cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

Migrate TC10.1.7 from TC12.1

Solution Partner Genius Solution Partner Genius
Solution Partner Genius

Good morning,

i've test the migration from TC10.1.7 to TC12.1.

In the new application root i need to update the xmls file for more feature.image.png

 

 

 

 

 

 

 

 

I select the *_feature.xml from my update BMIDE template (TC12 version) and AWC4.1 installation folder: more template are setting how "Install" or "Upgrade" but i've problem with two feature:

* Conflict with: feature.awsdotnetclient

* Conflict with: feature.awsclient

image.png

 

 

 

 

 

 

 

 

 

Can you help me?

Is it correct migrate directly to TC12 skipping the TC11 step?

 

Thank you very much,

have a nice day.

 

Francesco

8 REPLIES 8

Re: Migrate TC10.1.7 from TC12.1

Solution Partner Esteemed Contributor Solution Partner Esteemed Contributor
Solution Partner Esteemed Contributor
You need to stay true to your platform stack by choosing either awsclient (J2EE) or awsdotnetclient (.NET) but not both. Upgrading Tc10.1.7 to Tc12.1 is okay.

Randy Ellsworth, Teamcenter Architect, Applied CAx, LLC
NX 11 | SW 2016 | Creo 4 | TcUA 11.4
Evaluating: AW 3.4

Re: Migrate TC10.1.7 from TC12.1

Siemens Phenom Siemens Phenom
Siemens Phenom
upgrading from tc10 to tc12 is usually ok.
from the screenshots it seems like you already installed active workspace features in tc10 but haven't included the AWC media (original media location / update media location) when starting TEM - should make live a bit easier

Re: Migrate TC10.1.7 from TC12.1

Solution Partner Genius Solution Partner Genius
Solution Partner Genius

Good afternoon to all,

thank you for your tips and your answers.

Today i was able to start the migration but before start the upgrade i needed to "merge" the installation dvd: 

* Tc12.0.0.0_ActiveWorkspace4.1_wntx64\wntx64\install in Tc12.1.0.0_wntx64\wntx64\install

* Tc12.0.0.0_ActiveWorkspace4.1_wntx64\wntx64\modules in Tc12.1.0.0_wntx64\wntx64\module

* Tc12.0.0.0_ActiveWorkspace4.1_wntx64\wntx64\tc in Tc12.1.0.0_wntx64\wntx64\tc

So the conflicts are solved.

 

The migration started and worked until the step 197 where i've an error and stop with this message:

Step 197 of 359 - 54% Completed
Executing "aws2_install_tilecollections -u=infodba -p=***** -g=dba -mode=remove -file=%TC_INSTALL_DIR%/rb0reportingaw/data/rb0reportingawGatewayTilesCots_Upgrade_Remove.xml"
Application = "rb0reportingaw"
Section = "post-non-schema-add"
src_release = "NA"
tgt_release = "NA"
software_id = "NA"
Script File = "C:\Siemens\TC12\tcroot\install\rb0reportingaw\upgrade_rb0reportingaw_tc101.default"image.png

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

The command that give problem is this: "aws2_install_tilecollections -u=infodba -p=infodba -g=dba -mode=remove -file=%TC_INSTALL_DIR%/rb0reportingaw/data/rb0reportingawGatewayTilesCots_Upgrade_Remove.xml"

I've tried to start to run manually this command but i've the same problem:image.png

 

 

I've open the log file and this is the error:

image.png

 

 

 

 

 

 

 

I attach the log and shell*.err

 

Have you some tips to solve this error?

 

Thank you very much,

Francesco

Re: Migrate TC10.1.7 from TC12.1

Solution Partner Genius Solution Partner Genius
Solution Partner Genius

I've found on GTAC this workaround but doesn't work:

To work around this problem, you need to edit and remove three references
to aws2_install_tilecollections in the TC_ROOT/install/install/patch.xml file.

1) <tcexec cmd="aws2_install_tilecollections" parms="-u=${adminUser.user}
-p=${adminUser.password} -g=dba -mode=remove
-file=${app.path_s}/install/aws2/data/Awp0aws2GatewayTilesCots_Upgrade_Remove.x
ml" failonerror="true"/>

2) <tcexec cmd="aws2_install_tilecollections" parms="-u=${adminUser.user}
-p=${adminUser.password} -g=dba -mode=add
-file=${app.path_s}/install/aws2/data/Awp0aws2GatewayTilesCots_Upgrade_Add.xml"
failonerror="true"/>

3) <tcexec cmd="aws2_install_tilecollections" parms="-u=${adminUser.user}
-p=${adminUser.password} -g=dba -mode=update
-file=${app.path_s}/install/aws2/data/Awp0aws2GatewayTilesCots_Upgrade_Update.x
ml" failonerror="true"/>

Run TEM in recovery mode.

 

Francesco

Re: Migrate TC10.1.7 from TC12.1

Solution Partner Esteemed Contributor Solution Partner Esteemed Contributor
Solution Partner Esteemed Contributor
I can't find anything about Awp0ReportsTile, which is the dataset that TEM is attempting to delete. Neither is there sufficient online help for the aws2_install_tilecollections utility. Two suggestions:
1. Run aws2_install_tilecollections with "-h" to get the arguments accepted by the utility with a focus on "-mode=delete" and "bypass" (if exists).
2. Use the Rich Client, Print Object, to find the objects using the UID. This should help with the analysis to know what needs to be done next beyond calling GTAC.

Randy Ellsworth, Teamcenter Architect, Applied CAx, LLC
NX 11 | SW 2016 | Creo 4 | TcUA 11.4
Evaluating: AW 3.4

Re: Migrate TC10.1.7 from TC12.1

Solution Partner Genius Solution Partner Genius
Solution Partner Genius

Hi Randy,

the command aws2_install_tilecollections doesn't have a "-bypass" option and i'm unable to login in Teamcenter because i'm in the core of migration.

I've found a workaround to skip this command and go foward with the migration

I modified %_TC_ROOT%\install\rb0reportingaw\upgrade_rb0reportingaw_tc101.default commenting this line:image.png

 

 

 

 

The migration go without problem until the step 223 where i've another problem:image.png

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Reading the log file:

----------------------------------------------------------------------------
Step 223 of 358 - 62% Completed
Executing "install -tie_configbom_support infodba %TC_USER_PASSWD% dba"
Application = "foundation"
Section = "post-non-schema-delete"
src_release = "NA"
tgt_release = "NA"
software_id = "NA"
Script File = "C:\Siemens\TC12\tcroot\install\foundation\upgrade_foundation_tc101.default"
----------------------------------------------------------------------------
Command start time: ven mar 15 2019 12:09:30 AM Central European Time
Output:

Selected option: Install tables required for TIE Configured BOM Export.
Started POM v1000.0.1 ...
*** Caught an error while installing ... aborting!

Command end time: ven mar 15 2019 12:09:30 AM Central European Time
Command duration: 0.983 second(s)
Status: Failed with error code 1

I've tried to start the command manually but i've the same result:image.png

 

 

 

 

Reading the syslog file:

running POM install program: install -tie_configbom_support infodba <SECRET> dba

INFO - 2019/03/15-07:40:34.317 UTC - NoId - Default encryption configuration. - Teamcenter.FoundationBase at d:/workdir/tc121w1213_64/src/foundation/base/KeyManagerTcCrypto.cxx(138)
INFO - 2019/03/15-07:40:34.317 UTC - NoId - Using ODBC driver: DRIVER=SQL Server to attempt to connect.
- Teamcenter.POM at d:\workdir\tc121w1213_64\src\foundation\pom\eim\eim_trans_util.cxx(861)
**** Connected to 'DATABASE=TC10PROD;SERVER=SRVTC12DEV\TEAMCENTER' as 'infodba'
DBMS Version Information:
DBMS VERSION:: 13.0.5026.0 SP2 Standard Edition (64-bit)

DBMS Compatibility:: 130 version 13 level 0
DB:par: ArithAbort=1
POM_Parameter contents: Parameter = 'Value' (Status):
POM_ENABLE_LOCK_SERIALIZATION = '1' (Cached)
POM_INTERNAL_WHO_CLOSED_POM = '2019/03/14 23:28:45 infodba/infodba 00001048:000019cc srvtc12dev 1903141754\install-enq_support10480156.syslog' (Cached)
POM_INTERNAL_WHO_LOCKED_SCHEMA = '2019/03/14 18:08:17 infodba/infodba 0000109c:000010a0 srvtc12dev 1903141754\install-add_attr109c8eb5.syslog' (Cached)
INFO - 2019/03/15-07:40:34.336 UTC - NoId - Default encryption configuration. - Teamcenter.FoundationBase at d:/workdir/tc121w1213_64/src/foundation/base/KeyManagerTcCrypto.cxx(138)
INFO - 2019/03/15-07:40:34.337 UTC - NoId - POM V10.0.1.0 compiled on Dec 13 2018 - Teamcenter.POM at d:\workdir\tc121w1213_64\src\foundation\pom\pom\pom_init.cxx(461)
INFO - 2019/03/15-07:40:34.337 UTC - NoId - Compiled: -D__OCI -D__ODBC - Teamcenter.POM at d:\workdir\tc121w1213_64\src\foundation\pom\pom\pom_init.cxx(471)
Session is running in codeset 1252 17
INFO - 2019/03/15-07:40:34.339 UTC - NoId - Database Installation Identifier: "TEAMCENTER V10000.1.0.20130604" info=00000001 - Teamcenter.POM at d:\workdir\tc121w1213_64\src\foundation\pom\dds\dds_schemas.cxx(2811)
INFO - 2019/03/15-07:40:34.339 UTC - NoId - LOADING SCHEMA FILE: C:\Siemens\TC12\tcdata\pom_schema_SRVTC12DEV_TC10PROD - Teamcenter.POM at d:\workdir\tc121w1213_64\src\foundation\pom\dds\dds_schemas.cxx(3037)
INFO - 2019/03/15-07:40:34.385 UTC - NoId - Database Schema Cache Information: - Teamcenter.POM at d:\workdir\tc121w1213_64\src\foundation\pom\dds\dds_io.cxx(911)
d:\workdir\tc121w1213_64\src\foundation\pom\dds\dds_io.cxxINFO - 2019/03/15-07:40:34.392 UTC - NoId - Caching non-overrid class storage mode information.
- Teamcenter.POM at d:\workdir\tc121w1213_64\src\foundation\pom\dms\dms_class_storage_mode.cxx(1201)
INFO - 2019/03/15-07:40:34.394 UTC - NoId - Loaded schema has 1478 classes (17 versionable) and 5736 distinct attributes. - Teamcenter.POM at d:\workdir\tc121w1213_64\src\foundation\pom\dds\dds_schemas.cxx(3181)
INFO - 2019/03/15-07:40:34.395 UTC - NoId - REV: Versionable class found in schema. - Teamcenter.POM
EIM_set_lock_wait_time: Set lock wait time to 2 sec.
INFO - 2019/03/15-07:40:34.396 UTC - NoId - Caching non-overrid class storage mode information.
- Teamcenter.POM at d:\workdir\tc121w1213_64\src\foundation\pom\dms\dms_class_storage_mode.cxx(1201)
Cached flattened class information: Class Name = ClassID (Status) / Storage Mode:
Fnd0PreferenceCategory = 1348 (Cached) / flat
Fnd0AttrDescriptionInfo = 1354 (Cached) / flat
Fnd0PreferenceDefinition = 1349 (Cached) / flat
Fnd0PreferenceValue = 1350 (Cached) / flat
Fnd0DirectedLink = 1371 (Cached) / flat
Fnd0FileAccessAudit = 165 (Cached) / flat
Fnd0LicenseChangeAudit = 171 (Cached) / flat
Fnd0ScheduleAudit = 184 (Cached) / flat
Fnd0StructureAudit = 187 (Cached) / flat
Fnd0OAROpHistory = 1476 (Cached) / flat
Fnd0TcifEventStore = 1202 (Cached) / flat
Fnd0Message = 1191 (Cached) / flat
ImanExportRecord = 836 (Cached) / flat
Fnd0OARElement = 1420 (Cached) / flat
Fnd0OARFunction = 1421 (Cached) / flat
Fnd0LicenseExportAudit = 172 (Cached) / flat
Fnd0DigitalSignatureAudit = 1176 (Cached) / flat
Fnd0AuditLink = 494 (Cached) / flat
Fnd0OAROperation = 1422 (Cached) / flat
Fnd0GeneralAudit = 166 (Cached) / flat
Fnd0OAROperationGroup = 1423 (Cached) / flat
Fnd0OrganizationAudit = 180 (Cached) / flat
Fnd0OARRule = 1424 (Cached) / flat
Fnd0ConsentRecord = 1465 (Cached) / flat
Fnd0ContextSpecificID = 1466 (Cached) / flat
Fnd0SecurityAudit = 1196 (Cached) / flat
POM_stub = 19 (Cached) / flat
Fnd0LicenseLoginTimes = 1414 (Cached) / flat
Fnd0LoginLicenseInfo = 1417 (Cached) / flat
Fnd0SecondaryAudit = 185 (Cached) / flat
Fnd0WorkflowAudit = 192 (Cached) / flat
INFO - 2019/03/15-07:40:34.398 UTC - NoId - POM V10.0.1.0 startup finished. - Teamcenter.POM at d:\workdir\tc121w1213_64\src\foundation\pom\pom\pom_init.cxx(646)
WARN - 2019/03/15-07:40:34.411 UTC - NoId - TC_USE_KEYMANAGER environment variable is configured to not use KeyManager. - Teamcenter.FoundationBase at d:/workdir/tc121w1213_64/src/foundation/base/KeyManagerBcrypt.cxx(75)
POM ROW LOCKING MODE = Enhanced.
INFO - 2019/03/15-07:40:34.455 UTC - NoId - POM_login: "infodba" infodba / dba has logged in - Teamcenter.POM at d:\workdir\tc121w1213_64\src\foundation\pom\pom\pom_start.cxx(1295)
INFO - 2019/03/15-07:40:34.460 UTC - NoId - Started POM v1000.0.1 ... - Teamcenter.POM.install_main at d:\workdir\tc121w1213_64\src\foundation\pom\main\install_main.cxx(1201)
INFO - 2019/03/15-07:40:34.460 UTC - NoId - Default encryption configuration. - Teamcenter.FoundationBase at d:/workdir/tc121w1213_64/src/foundation/base/KeyManagerTcCrypto.cxx(138)
WARN - 2019/03/15-07:40:34.461 UTC - NoId - 208 - Tablespace infodba_ILOG specified in table creation doesn't exist. Trying ILOG tablespace - Teamcenter.POM at d:\workdir\tc121w1213_64\src\foundation\pom\dds\dds_build_env.cxx(807)
SCRATCH_TABLE already exists. Skipping creation and setting indexes....
SUBSCRIPTION_TABLE table already exists. Skipping creation...
ODBC error. SQLSTATE: 42000 Native error: 8111
Message: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot define PRIMARY KEY constraint on nullable column in table 'SUBSCRIPTION_TABLE'.
Approx SQL was "ALTER TABLE SUBSCRIPTION_TABLE ADD CONSTRAINT [pk_subscription_tbl] PRIMARY KEY CLUSTERED (app_id)"
ODBC error. SQLSTATE: 42000 Native error: 1750
Message: [Microsoft][ODBC SQL Server Driver][SQL Server]Could not create constraint or index. See previous errors.

Creating primary key pk_subscription_tbl on table SUBSCRIPTION_TABLE
*** EIM_check_error: code 8111
WARN - 2019/03/15-07:40:34.474 UTC - NoId - 545001 - (EIM_trans_util) [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot define PRIMARY KEY constraint on nullable column in table

 

I thinked that was a problem about the Compatibility Version but is it ok.

Have you some tips?

 

I attach a log files.

 

Thank you,

Francesco

Re: Migrate TC10.1.7 from TC12.1

Solution Partner Esteemed Contributor Solution Partner Esteemed Contributor
Solution Partner Esteemed Contributor
TEM created the SUBSCRIPTION_TABLE before it failed. Then you ran it on the command line and the creation of SUBSCRIPTION_TABLE was skipped. However, the command continued by trying to define a primary key on a column (pk_subscription_tbl) that has not been defined as "NOT NULL". The column needs to be defined as "NOT NULL" before adding "PRIMARY KEY CLUSTERED". You cannot have a null value as a key.

Call GTAC, they will either provide a fix or recommend that you roll back to the beginning and start over.

Randy Ellsworth, Teamcenter Architect, Applied CAx, LLC
NX 11 | SW 2016 | Creo 4 | TcUA 11.4
Evaluating: AW 3.4

Re: Migrate TC10.1.7 from TC12.1

Solution Partner Genius Solution Partner Genius
Solution Partner Genius

Hi guys,

sorry for the delayed answer.

I've solved the problem with GTAC help.

The problem was attributable at SUBSCRIPTION_TABLE: this table was created\modified by siteicons scripts and then return a problem during the deploy.

The table wasn't empty then i didn't drop it.

I renamed manually the table before run the new update: during the deploy I had the same error but clicking rerun on the panel the task continued without problem and the deploy was “Successfully”.

image.png

 

 

The table was recreated into the db during the upgrade but was empty unlike the old table that contained some rows: i've repopulate the table with the older values.

 

The migration ended fine and Teamcenter work fine.

 

I hope that this solution could be usefull.

 

Thank you very much,

Francesco