Elecció dels llocs a provar

Troubleshooting Teamcenter upgrade

Locate possible solutions to problems you may encounter during Teamcenter upgrade.

Problem Possible cause Solution

Cannot install four-tier rich client over-the-Web

Java Plug-in incorrectly installed Ensure that the Java Plug-in is installed correctly. For assistance, go to the following Web sites:

http://java.sun.com/products/plugin/ index.html#download http://java.com/en/download/help/ enable_browser.jsp http://java.com/en/download/help/ enable_panel.jsp

Incorrect Internet Explorer browser setting

Ensure that installing on demand is enabled:

Tools→Internet Options→Advanced→ Install on Demand

Ensure that scripting of Java applets is enabled:

Tools→Internet Options→Security→ Custom Level→Scripting of Java Applets

Errors when uploading or downloading files

FMS_HOME environment variable

does not point to the location of the File Management System (FMS) client executables

Incomplete installation of FMS client cache executables

Uninstall the rich client as described inUninstall the rich client. Then reinstall the rich client.

Caution Always uninstall a rich client using this procedure before installing a new rich client.

Incompatible configurations of FMS If two rich clients are installed on the workstation, report the errors to the Teamcenter administrator.

When two rich clients are installed on the same workstation, FMS uses the FMS_HOME value set during the first installation. The configuration of the file client cache (FCC) to a file server cache (FSC) must support both deployments, especially if the second deployment is to a different database.

Teamcenter displays an error message when you attempt to access Teamcenter online help

Teamcenter administrator did not include online help when configuring your rich client

Problem Possible cause Solution

Unable to view or to search Teamcenter online help

The Web browser you are using does not meet requirements to view and search Teamcenter online help

Make sure you are using a Siemens PLM Software-supported Web browser. For information about supported Web browsers, see the Siemens PLM SoftwareCertification Database.

Databases dating from before iMAN 4.0 have two iMAN_drawing relation types

IMAN_drawing relation types from

two previous iMAN versions exist in your database.

Before iMAN 4.0, an IMAN_drawing relation was defined but never used. At version 7.0, an IMAN_Drawing relation was defined and used in ProductVision. If you have a database that originated from a pre-iMAN 4.0 version, you may have an

IMAN_drawing relation defined. If so, the Business Modeler IDE

does not find it in the standard set of definitions and includes it in the customer template definition.

If you have a pre-iMAN 4.0 version database, reconcile the relation type definitions before running the Teamcenter 10.1 upgrade by typing the following command:

install_types –u=infodba -p=password -g=dba -f=delete -t=IMAN_drawing -c=ImanRelation

If you run this utility on a later database, you get the following error, which you can ignore:

Type IMAN_drawing for Class ImanRelation does not exist

To get a complete list of types installed in your database, type the following command:

install_types u=infodba -p=password -g=dba -f=list

This lists the several hundred types available. Teamcenter upgrade

fails with custom types

A custom data type has the same name as the parent class.

If you have a custom type name with the same name as the parent class, the custom type is identified and added to the custom templates, but the upgrade fails. For example, you have a custom

storage_media type that belongs to the storage_media class.

Before upgrading to Teamcenter 10.1, rename the custom type name to anything other than the parent class. For example, rename the storage_media type to storage_media_custom before you upgrade.

Teamcenter upgrade fails with large database issues

The database is not sized properly. If your upgrade changes or deletes a large number of records, it can fail if the database is not sized properly. Oracle displays an error similar to the following:

ORA-01652: unable to extend temp segment by 128 in tablespace TEMP

The following upgrade examples can lead to this error:

install -mod_attr infodba ${TC_USER_PASSWD} dba POM_application_object owning_user POM_attr_no_pom_backpointer +

install -mod_attr infodba ${TC_USER_PASSWD} dba POM_application_object last_mod_user POM_attr_no_pom_backpointer +

These commands update many rows in the pom_backpointer table. The number of rows updated is approximately three times the size of the ppom_application_object table. You can determine the table size with the following SQL command:

SELECT COUNT(puid) FROM ppom_application_object;

To resolve this issue, you must have a large undo or rollback tablespace and a large TEMP tablespace. Increase the size of both the TEMP and undo tablespaces to at least 5 GB each.

1. Use the following SQL command to determine where the data files reside:

SELECT tablespace_name,file_name FROM dba_data_files;

Problem Possible cause Solution TABLESPACE _NAME FILE_NAME SYSTEM D:\ORACLE\ORADATA\SYSTEM01.DBF UNDOTBS1 D:\ORACLE\ORADATA\UNDOTBS01.DBF SYSAUX D:\ORACLE\ORADATA\SYSAUX01.DBF IDATA D:\ORACLE\ORADATA\IDATA01.DBF ILOG D:\ORACLE\ORADATA\ILOG01.DBF INDX D:\ORACLE\ORADATA\INDX01.DBF

In this case, all data files are located in the

D:\ORACLE\ORADATA directory.

2. Add a data file to the TEMP tablespace:

ALTER TABLESPACE TEMP ADD tempfile ’D:\ORACLE\ORADATA\temp2.dbf’ size 5000M;

3. Add a data file to the undo tablespace:

ALTER TABLESPACE UNDOTBS01 ADD datafile ’D:\ORACLE\ORADATA\’ undotbs2.dbf size 5000M;

To help ensure the upgrade is successful, make sure the redo logs are sized properly (100M each) and reside on a separate disk from the data. If necessary, resize the redo logs.

1. Set the ORACLE_SID environment variable.

2. Log on to Oracle:

sqlplus /nolog

connect system/password as sysdba;

3. Find the list of the redo log groups and see where the files reside.

SELECT GROUP#,TYPE,STATUS,MEMBER FROM V$LOGFILE;

The results may look like this:

3 ONLINE STALE E:\ORACLE\ORADATA\DPVPERF\REDO03.LOG 2 ONLINE E:\ORACLE\ORADATA\DPVPERF\REDO02.LOG 1 ONLINE STALE E:\ORACLE\ORADATA\DPVPERF\REDO01.LOG

4. Create the new redo logs as follows. You can change the drive where you can create these, but redo logs should reside on a separate disk from the data.

ALTER DATABASE ADD LOGFILE GROUP 4 (’E:\ORACLE\ORADATA\DPVPERF\ REDO04.LOG’) SIZE 100M;

ALTER DATABASE ADD LOGFILE GROUP 5 (’E:\ORACLE\ORADATA\DPVPERF\ REDO05.LOG’) SIZE 100M;

ALTER DATABASE ADD LOGFILE GROUP 6 (’E:\ORACLE\ORADATA\DPVPERF\ REDO06.LOG’) SIZE 100M;

5. Run the following command to force the log switch:

ALTER SYSTEM SWITCH LOGFILE;

6. (Optional) Drop redo log groups 1, 2, and 3:

ALTER DATABASE DROP LOGFILE GROUP 1; ALTER DATABASE DROP LOGFILE GROUP 2; ALTER DATABASE DROP LOGFILE GROUP 3;

Problem Possible cause Solution

Note If the group number is the current group and you cannot drop it, run the command to force the log switch to make group 4, 5, or 6 current. Rich client startup

performance is slow

Wait time for hierarchy tree checked-out icon display.

Set theTC_show_checkedout_iconpreference to FALSE.

Note Users and administrators can set the

TC_show_checkedout_iconpreference to

TRUE to enhance usability or to FALSE to enhance

rich client startup performance.

For more information, see thePreferences and Environment Variables Reference.

FCC in Engineering Process Management hangs after upgrade to Teamcenter 10.1

Engineering Process Management FCC attempting to use JRE from Teamcenter 10.1.

Configure the Engineering Process Management FCC to use its own JRE.

Different versions of Teamcenter work with different versions of Java. For example, Teamcenter engineering process management 2005 SR1 works with Java 1.4, Teamcenter 8.3 works with Java 1.5, and so on.

If you are running multiple versions of Teamcenter on your system and they work with different versions of Java, you must configure your FMS client caches (FCCs) to use the Java run-time environments (JREs) with which they were installed.

1. Open the FMS_HOME/startfcc.sh (UNIX systems) file or the FMS_HOME\startfcc.bat (Windows systems) file in a plain text editor.

2. Set the FCC_JAVA environment variable to the JRE supplied with the Teamcenter version with which the FCC was installed.

For information about versions of operating systems, third-party software, Teamcenter software, and system hardware certified for your platform, see the Siemens PLM SoftwareCertification Database.