DBMS_PIPE:A Summary of Configurations
From: Nicholas Wee <scornd11_at_technet.sg>
Date: 17 Nov 1994 00:13:18 GMT
Message-ID: <3ae76v$o1v_at_raffles.technet.sg>
A summary of DBMS_PIPE issues faced:
Date: 17 Nov 1994 00:13:18 GMT
Message-ID: <3ae76v$o1v_at_raffles.technet.sg>
A summary of DBMS_PIPE issues faced:
PS: Thanks to all those who replied...!
- DBMS_PIPE is NOW easy and fun to use, but beware of certain configuration steps.
- For the developer's userid and the user's userid, remember to grant execute the procedure revelant procedures to them.
- Once this ok, the stored procedures or functions you build can be compiled successfully.
- The examples involving PL/SQL blocks in Pro*C cannot work immediately.
You need to modify the proc.mk file. One way is as follows.
After the section
PROC=$(ORACLE_HOME)/bin/proc
PROFOR=$(ORACLE_HOME)/bin/profor PROCOB=$(ORACLE_HOME)/bin/procob PROPAS=$(ORACLE_HOME)/bin/propas PROADA=$(ORACLE_HOME)/bin/proada
and before the section
PROFLAGS=ireclen=132 oreclen=132 select_error=no $(SQLCHECK) $(PROUSER)
add
SQLCHECK=sqlcheck=semantics
PROUSER=userid=userid/userpassword
where userid and userpassword are that of the developer. Oracle checks to ensure that the objects which u specify exist in the schema.
5. With this in mind, compilation should be a breeze.
Thanks again. Received on Thu Nov 17 1994 - 01:13:18 CET