CRM Tables with NOLOGGING
Hi all,
We have an old CRM 9.0 application, it has been updated with new PeopleTools and Bundles. Right now we have a problem, if we launch a report to count the number of tables configured with NOLOGGING option we find many SYSADM objects.
The query:
SELECT OWNER, TABLE_NAME, STATUS
FROM DBA_TABLES
WHERE LOGGING = 'NO'
AND OWNER NOT IN ('SYS')
ORDER BY OWNER;
Returns about 50 standard PeopleSoft application objects.
Do you know if PeopleSoft CRM needs standard tables to be configured with NOLOGGING?
Is there any possible impact to changing this objects to LOGGING (excluding the performance difference)?
Have you ever seen this configuration on any other PeopleSoft CRM application?
We have an old CRM 9.0 application, it has been updated with new PeopleTools and Bundles. Right now we have a problem, if we launch a report to count the number of tables configured with NOLOGGING option we find many SYSADM objects.
The query:
SELECT OWNER, TABLE_NAME, STATUS
FROM DBA_TABLES
WHERE LOGGING = 'NO'
AND OWNER NOT IN ('SYS')
ORDER BY OWNER;
Returns about 50 standard PeopleSoft application objects.
Do you know if PeopleSoft CRM needs standard tables to be configured with NOLOGGING?
Is there any possible impact to changing this objects to LOGGING (excluding the performance difference)?
Have you ever seen this configuration on any other PeopleSoft CRM application?
0