Data cleansing Note: When multiple users call the same function, note that multiple users
Original Works are from the blog of "Deep Blue blog". You are welcome to repost them. You must specify the source when you repost them. Otherwise, you have the right to pursue legal liability for copyright.
Deep Blue blog: http://blog.csdn.net/huangyanlong/article/details/46340515
Background]
During data extraction, when multiple users access different tables on the source end and need to use the same function, they need to create a new one under multiple users.
[Solution]
When multiple users use the same function, we can choose to recreate the function, but sometimes the execution is inconvenient due to too many functions, it is sometimes difficult for every user to manage functions once. Therefore, we can create the aggregate function and grant permissions to multiple users to use the same function. Take the isnum () function for example, the syntax is grant execute on user. function name to other users.
[Experiment]
Before granting permissions, log on to hyl and use the isnum function. The following error is returned:
Grant the isnum function execution permission of scott to the hyl user under sys, as follows:
SQL> grant execute on scott. isnum to hyl;
Use hyl again to call the isnum function. The verification is as follows:
Small knowledge, easy to remember.
**************************************** ***************************** *******************
Original works, from the blog of "Deep Blue". You are welcome to reprint them. Please indicate the source (Http://blog.csdn.net/huangyanlong).
Series link _ 20150523
Blue growth note-chasing DBA (1): traveling on the road to Shandong
Blue growth notes-Chase DBA (2): Install! Install! Long-lost memories have aroused my new awareness of DBAs.
Blue growth note-chasing DBA (3): importing and exporting data on antiques becomes a problem
Blue growth note-chasing DBA (4): recalling the sorrow of teenagers, and exploring oracle Installation (10g and 11g in Linux)
Blue growth note-chasing DBA (5): Not talking about technology or business, annoying Application Systems
Blue growth note-chasing DBA (6): doing things and being human: Small technology, great human
Blue growth note-Chase DBA (7): Basic commands, foundation stone
Blue growth notes-chasing DBA (8): repicking SP reports and recalling oracle's STATSPACK Experiment
Blue growth note-chasing DBA (9): Chasing DBA, new planning, new departure
Blue growth note-chasing DBA (10): Flying knife defense, familiarity rather than expertise: Playing with middleware Websphere
Blue growth note-chasing DBA (11): It's easy to go home and wake up.
Blue growth notes-Chase DBA (12): seven days and seven gains of SQL
Blue growth note-chasing DBA (13): Coordinating hardware manufacturers, six stories: what you see as "servers, storage, switches ......"
Blue growth note-chasing DBA (14): An unforgettable "Cloud" end, started hadoop deployment
Blue growth note-chasing DBA (15): Who thinks FTP is "simple" and thinks it is a trigger
Blue growth note-chasing DBA (16): DBA also drank alcohol and was rejected
**************************************** **************************************** **********************************
**************************************** ***************************** *****************
Original works, from the blog of "Deep Blue". You are welcome to reprint them. Please indicate the source (Http://blog.csdn.net/huangyanlong).
Series link _ 20150528:
Football and oracle series (1): 32-way zhoudianbing, overall view of group A Brazil smon process of oracle32 process Alliance
Football and oracle series (2)
Football and oracle series (3): oracle process rankings, the World Cup round is about to fight!
Football and oracle series (4): from Brazil to Germany, think of the different RAC topology comparison!
Football and oracle series (5): The directX library missing in the voda14 game is similar to the oracle rpm package!
Football and oracle series (6): Asian Cup with database creation-come on, Chinese Team
**************************************** **************************************** **********************************