Ò׽ؽØÍ¼Èí¼þ¡¢µ¥Îļþ¡¢Ãâ°²×°¡¢´¿ÂÌÉ«¡¢½ö160KB

Oracle Workflows Access Protection Concepts

Oracle Workflows Access Protection Concepts
As a workflow developer, you can use access protection to allow or discourage “customers” of your workflows from modifying your “seed data” workflow definitions.
×÷Ϊ¹¤×÷Á÷¿ª·¢Õߣ¬Äã¿ÉÒÔÀûÓ÷ÃÎÊ¿ØÖƱ£»¤È¨ÏÞÀ´ÔÊÐí»ò×èÖ¹¹¤×÷Á÷µÄʹÓÃÕßÐÞ¸ÄÄã×îÖÕ
¶¨ÒåµÄ¹¤×÷Á÷¡£
As a customer of predefined workflows provided by Oracle, you can use access protection to preserve valid customizations you have made to a predefined workflow during a workflow definition upgrade.
×÷Ϊ¼×¹ÇÎÄÌṩµÄÔ¤¶¨Ò幤×÷Á÷£¬Äã¿ÉÒÔÀûÓ÷ÃÎÊ¿ØÖÆÈ¨ÏÞÀ´±£»¤Äã¶Ô¹¤×÷Á÷µÄÓÐЧµÄ¿Í»§»¯Éý¼¶¡£
All workflow objects except lookup codes, function attributes, and message attributes contain an Access tab in their property pages.  Lookup codes, function attributes, and message attributes inherit their access settings from their parent lookup type, function, or message, respectively.
³ýÁËLookup´úÂ룬º¯ÊýÊôÐÔºÍÏûÏ¢ÊôÐÔµÄÆäËûËùÓй¤×÷Á÷¶ÔÏó¶¼°üº¬¿ØÖÆÊôÐÔ±êǩҳ¡£Loopup£¬º¯ÊýÊôÐÔºÍÏûÏ¢ÊôÐÔ·Ö±ð¼Ì³ÐËüÃǸ¸ÀàÐ͵ķÃÎÊ¿ØÖÆÈ¨ÏÞ¡£
The Access tab lets you define whether:
•Future customizations to the object are preserved during a workflow definition upgrade.
•The object can be edited by users operating at a higher access level.
 ·ÃÎʱêÇ©¿ÉÒÔÈÃÄ㶨ÒåÊÇ·ñ£º
ÔÚ¹¤×÷Á÷Éý¼¶µÄʱºò£¬±£»¤Î´À´¾­¹ý¿Í»§»¯µÄ¶ÔÏó
¶ÔÏó¿ÉÒÔÔÚ¸ü¸ßµÄ·ÃÎʼ¶±ðÉϱ»±à¼­¡£
ACCESS LEVELS
·ÃÎʼ¶±ð
Each user of Oracle Workflow Builder operates the system at a certain access level.
The access levels are defined as follows:
ü       0-9: Reserved for Oracle Workflow
ü       10-19: Reserved for Oracle Application Object Library
ü       20-99: Reserved for Oracle E-Business Suite
ü       100-999: Reserved for customer organizations
ü       1000: Public
ÿ¸ö Oracle Workflow Builder µÄʹÓÃÕ


Ïà¹ØÎĵµ£º

¡¾oracle֪ʶÊÕ¼¯¡¿ÏµÍ³ÊÓͼºÍÓû§È¨ÏÞ

ORACLEÖÐÊý¾Ý×ÖµäÊÓͼ·ÖΪ3´óÀà,     ÓÃÇ°×ºÇø±ð£¬·Ö±ðΪ£ºUSER£¬ALL ºÍ DBA£¬Ðí¶àÊý¾Ý×ÖµäÊÓͼ°üº¬ÏàËÆµÄÐÅÏ¢¡£
USER_*:ÓйØÓû§ËùÓµÓеĶÔÏóÐÅÏ¢£¬¼´Óû§×Ô¼º´´½¨µÄ¶ÔÏóÐÅÏ¢
ALL_*£ºÓйØÓû§¿ÉÒÔ·ÃÎʵĶÔÏóµÄÐÅÏ¢£¬¼´Óû§×Ô¼º´´½¨µÄ¶ÔÏóµÄÐÅÏ¢¼ÓÉÏÆäËûÓû§´´½¨µÄ¶ÔÏ󵫸ÃÓû§ÓÐȨ·ÃÎʵÄÐÅÏ¢
DBA_* ......

OracleÓû§¡¢½ÇÉ«¡¢È¨ÏÞºÍϵͳ×ÊÔ´¹ÜÀí³£ÓòÙ×÷

²éѯÓû§ÐÅÏ¢
SELECT USERNAME,DEFAULT_TABLESPACE, TEMPORARY_TABLESPACE, PROFILE, ACCOUNT_STATUS, CREATED from dba_users; ²éѯÓû§¿Õ¼äʹÓúÍÉÏÏÞÇé¿ö
SELECT username, tablespace_name, bytes/1024/1024 space_used_in_mb, max_bytes/1024/1024 max_space_in_mb from dba_ts_quotas; ´´½¨ ......

110¸öoracle³£Óú¯Êý×ܽá

1. ASCII
·µ»ØÓëÖ¸¶¨µÄ×Ö·û¶ÔÓ¦µÄÊ®½øÖÆÊý;
SQL> select ascii(A) A,ascii(a) a,ascii(0) zero,ascii( ) space from dual;
A A ZERO SPACE
--------- --------- --------- ---------
65 97 48 32
2. CHR
¸ø³öÕûÊý,·µ»Ø¶ÔÓ¦µÄ×Ö·û;
SQL> select chr(54740) zhao,chr(65) chr65 from dual;
ZH C
-- -
ÕÔ A
......

ORACLE Ò»Ö¶Á(Consistent Read)µÄ²½Öè

1. Read the Data Block.
2. Read the Row Header.
3. Check the Lock Byte to determine whether there's an ITL entry.
4. Read the ITL entry to determine the Transaction ID (Xid).
5. Read the Transaction Table using the Transaction ID. If the transaction has been committed and has a System Commit ......
© 2009 ej38.com All Rights Reserved. ¹ØÓÚE½¡ÍøÁªÏµÎÒÃÇ | Õ¾µãµØÍ¼ | ¸ÓICP±¸09004571ºÅ