Community Tip - When posting, your subject should be specific and summarize your question. Here are some additional tips on asking a great question. X
Solved! Go to Solution.
We were able to resolve the issue working with our DBA.
The issue was caused by specific LOB object SYS_LOB0000051289C00001$$ associated with the WINDCHILLDB.COLLECTORCACHE table. Despite applying the latest patch, the error persisted.
To address the issue, the following actions were taken:
1.A backup of the COLLECTORCACHE table was created.
2.The table was truncated to clear its contents.
3.As per CS44106, row movement was enabled for the table using the command:
ALTER TABLE COLLECTORCACHE ENABLE ROW MOVEMENT;
DBA confirmed all is ok on the DB side. However still the add to workspace window keeps loading.
contacting PTC Technical Support is your quickest way to resolve this issue. you did not mention which CAD solution you are working with or how your storage is setup in Windchill. when i see these types of DB error messages, i check table space in the DB, but when its full, many actions in Windchill will not work. it would be good to know if this happens for all users, one user or admin user.
adding to a workspace does not require any client side software, so it should be easy enough to debug. definitely change the log file output in Windchill to get more details.
We checked with DBA, rebuild index, run db statistics and confirmed Oracle Flash Recovery Area (FRA) has enough sufficient free diskspace.
We are trying a Creo CAD object to add to workspace from a stand alone browser.
We enabled pom loggers, however it is prety much printing the same thing.
The ORA 600 error message is defined as a generic DB error in the CS Article @Fadel provided. Is there any more detail in the log file?
We were able to resolve the issue working with our DBA.
The issue was caused by specific LOB object SYS_LOB0000051289C00001$$ associated with the WINDCHILLDB.COLLECTORCACHE table. Despite applying the latest patch, the error persisted.
To address the issue, the following actions were taken:
1.A backup of the COLLECTORCACHE table was created.
2.The table was truncated to clear its contents.
3.As per CS44106, row movement was enabled for the table using the command:
ALTER TABLE COLLECTORCACHE ENABLE ROW MOVEMENT;