Oracle 11g & Windchill 9.1

[PreetiGupta]

We are running our Windchill 9.1 M040 system on Oracle 10G (Windows 64 bit 2003 server).

We planning to upgrade Oracle to 11G(64 bit) version on the same Windows 64 bit 2003 server. We always ran 32 bit Oracle with Windchill for 3 years now.

Anybody running Oracle 11G 64bit in production 9.1? Please share your experience.

Thanks,
Preeti

[MorganBelais]

Hello,

We are running Windchill 9.1 with Oracle 10g 64 bits on Oracle enterprise (Redhat bundled by Oracle)

We plan to move to Oracle RAC 11G 64 bits linux this summer.

[nbouayad]

Dear Preeti,

I do not know about Windows XP 64,but we are using Oracle 11g + Windchill/PDMLink 9.1 M040 under Windows 7/64 bits without any problem.

Hope that helps.

Regards.

Nassim.

---

Nassim BOUAYAD-AGHA

Software developer/architect

http://www.wincom-consulting.co.uk

[nbouayad]

Please note that even if you get Warnings while installing Oracle 11g under Window7/64,the installation works.

[SteveVinyard]

The only downside to Oracle 11 is that it does not have a tuner package from PTC yet.

[nbouayad]

Steve,

You are right!

But I can tell you that I can find a real difference using Windchill and Oracle 11G on Windows7/64.Performance is great!

[PreetiGupta]

We do not use PTC tuner for Oracle 10G also. Performance is good right now, hoping to get better with Oracle 11G 🙂

Thanks for the feedback.

[nbouayad]

Another useful information,Oracle 10G installation does not work under Windows7/64.

[atwood]

As long as you pay attention to the ADDM reports and keep the stats job running regularly, you shouldn't need the PTC Tuner package for 10g or 11g. It has become redundant after 9i.

Tim Atwood

In Reply to Preeti Gupta:

We do not use PTC tuner for Oracle 10G also. Performance is good right now, hoping to get better with Oracle 11G 🙂

Thanks for the feedback.

[patrick.chin1]

Got some very good advicecombine with the help of PTC technical support to start using 16K block size instead of 8K which is required by Oracle 11G on 64bit:

• First create the database manually and make sure you have all the tablespaces with the same or slightly more than the current production system
  • BLOBS, INDX, WCAUDIT, TEMP,USERS...
• Follow SPR instructions 1466057:

Add this to your site.xconf and then run xconfmanager -p:

<property name="wt.generation.sql.tinyBlobSize" overridable="true"&lt;br"/> targetFile="codebase/user.properties"
value="32k"/>
<property name="wt.generation.sql.smallBlobSize" overridable="true"&lt;br"/> targetFile="codebase/user.properties"
value="32k"/>

From a windchill shell/environment command, run this command:

$WT_HOME/bin/JavaGen.sh registry false false true false false

or

%WT_HOME%\bin\JavaGen.bat registry false false true false false

This should update all your sql commands to make sure the incremental tablespace size is set to 32K.

You can now point to the database to either install a new Windchill system or create a new user with the same oracle permissions: Connect, Resource, Query rewrite, Create sequence, Create index

Unless someone else has figured it out, when importing from and to users, we found out since Windchill 7.0, the windchill oracle user name has to be identical. You should be golden after that with pointing your windchill systemto the new oracle database in site.xconf:

<property name="wt.pom.serviceName" overridable="true" targetfile="db/db.properties"&lt;br"/> value="<oracle_hostname>:1521:<sid>"/>

<property name="wt.pom.jdbc.host" overridable="true" targetfile="db/db.properties"&lt;br"/> value="<oracle_hostname>"/>

If you installed partslink:

<property name="nitidus.sqlcache.db.host" overridable="true"&lt;br"/> targetFile="partslink/conf/main.properties"
value="<oracle_hostname>"/>

Hope these tips help.

[PreetiGupta]

Thanks Patrick for this info. Always more to story 🙂