Troubleshooting
Problem
This document discusses how the system determines the schema in which an unqualified object will be created when using the SQL naming convention.
Resolving The Problem
This document discusses how the system determines the schema in which an unqualified object will be created when using the SQL naming convention.
If you are creating an object in SQL using SQL naming convention and you do not qualify the object, the system will by default create the object in the schema that matches the profile name. For example, if you create a view as follows:
CREATE VIEW MA_PROJ
AS SELECT * FROM PROJECT
WHERE SUBSTR(PROJNO, 1, 2) = 'MA'
and you are signed on with the profile QSECOFR and there is no QSECOFR schema, the operation will fail with message SQL0204 - QSECOFR in QSYS type *LIB was not found.
To correct the problem, you must qualify the view name or use the system naming convention.
SQL v. System naming can be set on the various interfaces.
For example with STRSQL, you can set it via F13, and "1. Change session attributes "
Historical Number
624957733
Was this topic helpful?
Document Information
Modified date:
18 December 2019
UID
nas8N1011136