Problem: The user attempted to use a StarSQL SQL package that he or she does not have permission to use or execute.

Solution: The DBA must grant the user permissions to run/execute the StarSQL SQL Packages. We recommend that use/execute access to StarSQL packages be granted to PUBLIC. For more information about the StarSQL static packages, see the StarAdmin Help or the StarSQL Help.

Error reported by server during bind of package.

Problem: The user does not have permission to bind the StarSQL packages in the library specified in the Package Collection Name field or the package already exists.

Solution: If you are using StarSQL for the first time, we recommend that you use StarAdmin to bind a complete set of packages. Refer to the technical document How to Bind Packages with StarAdmin for instructions.

Otherwise, check with your DBA to ensure that you have permission to write to the library specified as the Package Collection Name in your StarSQL data source configuration. If you already have packages in this library and you need to rebind them, drop the packages first before attempting to create new ones.

If your database is DB2 for OS/390 or z/OS, DB2 for VSE & VM (SQL/DS) or DB2 for Linux, UNIX, and Windows:

Problem: The user does not have permission to bind the StarSQL packages in the collection specified in the Package Collection Name field or the package already exists.

Solution: Check with your DBA to make sure you have CREATEIN and BINDADD authority on the package collection specified in the StarSQL data source. If you already have a static package, drop the package first before creating a new one. For more information about the StarSQL static packages, see the StarAdmin Help and the StarSQL Help.

Database server <database server name> not found.

Problem: The Database Server Name specified in the StarSQL data source setup for AS/400 does not match the relational database directory entry.

Solution: Check the relational database directory entry using the command WRKRDBDIRE. If no entry exists with a location of (*LOCAL), add one.

If your database is DB2 for OS/390 or z/OS, or DB2 for VSE & VM (SQL/DS):

Problem: The Database Server Name specified in the StarSQL data source setup for does not match the relational database name on the host.

Solution: Verify that the value in the Database Server Name field of the StarSQL data source setup is the host's DDF location name. For DB2 on OS/390 or z/OS, the database server name can be found by running the VTAM change log inventory utility (DSNJU003) or through panels by using DSNTIPR. The line will look like this:

DDF LOCATION= SYDNEY, LUNAME=LUDBD1(PASSWORD=....)

You can also determine the location name of DB2 in DDF by one of the following methods:

Stop/Start DDF. When you start DDF, you will see the location name as well as the LU name for DB2.

Check the syslog for a DB2 message DSNL004I (=DDF started ok). The location name will be here as well.

Section number not valid (#144).

Problem: You are using static packages on DB2 that are incompatible with either your new DB2 system or with the new version of your StarSQL driver.

Solution: After upgrading StarSQL or your DB2, you must drop (or delete) the old StarSQL static packages and bind (create) new static packages. Drop or delete the packages manually on the DB2 host. To bind a new set of packages, follow the instructions in the technical document How to Bind Packages with StarAdmin.

<authid> does not have the privilege to perform operation execute on <STARSQL>.SWRC0000

Problem: The user attempted to use a StarSQL static package that he or she does not have permission to use.

Solution: By default, only the user who bound the static package can use it; the DBA or another user with equivalent authority must grant other users permission to use or execute the StarSQL static packages. You can use StarAdmin to grant execute authority to PUBLIC. For more information about the StarSQL packages, see the StarAdmin Help or the StarSQL Help.

Problem: The user does not have permission to bind the StarSQL packages in the collection specified in the Package Collection Name field or the package already exists.

Solution: Check with your DBA to make sure you have CREATEIN and BINDADD authority on the package collection specified in the StarSQL data source. If you already have a static package, drop the package first before creating a new one. For more information about the StarSQL static packages, see the StarAdmin Help and the StarSQL Help.

Unexpected DRDA reply codepoint x`2208`

Problem: The user attempted to bind (or create) a static package in a collection in which he is not permitted to bind packages.

Solution: Obtain the necessary DB2 permissions to bind static packages, or request that the DBA bind these packages for you.In order to bind the StarSQL static packages, the user needs both BINDADD and CREATE IN authority. For more information about the StarSQL static packages, see the StarAdmin Help and the StarSQL Help.

Unexpected DRDA reply codepoint x`1254`

Problem: You will get this error if the Database Server Name specified in the StarSQL data source setup for AS/400 via Microsoft Host Integration Server does not match the relational database directory entry for the AS/400 identified by your Remote LU in Network Setup. You can also get a similar error if you are attempting to bind packages and you do not have sufficient authority on the AS/400.

Solution: Check the relational database directory entry for the AS/400 using the command WRKRDBDIRE. If no entry exists with a location of (*LOCAL), then add one. Also make sure that the Remote LU named in the data source is the one you wish to reach. If you get this error when you are attempting to bind packages, check with your AS/400 Administrator ensure that you are able to write to the library specified as the Package Collection Name. For more information, see the StarSQL Help.