Yes, technically you can change the default PeopleSoft schema owner from SYSADM to another user. However, this is not recommended and is rarely done in practice due to the depth of integration PeopleSoft has with the SYSADM schema.
PeopleSoft systems (especially for Oracle) are designed with tight coupling to the SYSADM schema:
- The entire application structure—including tables, views, indexes, stored procedures—assumes SYSADM as the owner.
- Application Designer, Data Mover, and many internal processes reference SYSADM explicitly.
- Security roles and access privileges are often tied to this schema.
Implications of changing the schema owner
Switching away from SYSADM introduces significant risks and complexity:
Technical Impact
- Tool compatibility: PeopleSoft tools expect SYSADM as the schema; changing it could break connections or tooling behavior.
- Customization burden: You’ll need to modify scripts, grants, security roles, and configuration files to align with the new schema owner.
- Patches and upgrades: Oracle-delivered updates assume SYSADM. Future upgrades could fail or require heavy re-engineering.
Security Impact
- Permission drift: Ensuring your new user matches SYSADM's permissions involves detailed auditing and scripting.
- Compliance concerns: Changing schema ownership might impact external audits or vendor support agreements.
Supportability
- Oracle and PeopleSoft support may be limited or withdrawn if you move outside standard configurations.
Recommended Practice
Stick with SYSADM as the schema owner unless you have an extremely compelling architectural or security requirement—and even then, consult deeply with Oracle or PeopleSoft technical architects before proceeding.
