Implementing Lawson Security Constraints in the Database
Use this procedure to duplicate Infor Lawson table level security in the Oracle database.
When you make changes to any of your Infor Lawson table-level security constraints, run bldora11sec
to implement the changes in the Oracle database.
When you drop and recreate any tables either by using the bldora11sec / bldora12sec
utility
or by reorganizing the database, you also drop all security constraints on
those tables in the Oracle database. Run bldora11sec
again
to reinsert your table-level constraints.
To implement security constraints in the database
bldora11sec [-UDGVq]
[-u DbLoginName] [-p Password] DataArea
DatabaseService
Consider the following options:
Option | Description |
---|---|
-u DbLoginName
|
The database user login. |
-p Password
|
The password for the database user. |
-U
|
Update mode. Issue query directly to the database. |
-D
|
Drop-only processing; revoke all permissions from all Lawson tables for all Lawson users. Once Lawson table-level security
exists in the Oracle database, generate SQL statements to remove it by
running the |
DataArea
|
The data area that you want to apply security to. |
DatabaseService
|
Lawson Security only. The name of the database service defined for your system. For each RMId, |
V
|
Print the version. |
-q
|
Do not print the commands to stdout .
|