Uninstall/Remove Sql plus

Hai,
I have an server in which Oracle 9i Standard Edition has been installed. If i dont want to give access to sqlplus from that server, whether deletion of sqlplus.exe alone will be sufficient or any thing else needs to be done.
Regards
Sridhar

user7277731 wrote:
Hai,
I have an server in which Oracle 9i Standard Edition has been installed. If i dont want to give access to sqlplus from that server, whether deletion of sqlplus.exe alone will be sufficient or any thing else needs to be done.
There is no need to delete the files .. If you delete that , even you cannot login to server as sysdba through sql plus.
You can change permission of sqlplus.exe , so that other users are not able to execute this.
Regards
Rajesh

Similar Messages

Block Sql Plus Login

Hi,
I have database 8.05. For client server application on the client side we mention
D:\ORACLE\BIN\F50RUN32.EXE c:\test\test.fmx test/test@test
Now anyone can logon to sql plus and if he knows sql plus as the username and password is there. I dont want to remove sql plus from each machine and at the same time i dont want to user to logon to sql prompt.
Operation system is windows NT.
Rgds

What you need to do is , give only CONNECT permissions to user TEST. So even if the user logs in SQLPLUS he wont be able to access any OBJECTS.
ALSO you need to create another Oracle user , which will have all the necessary permissions.
In your client application (FORMS), you need to connect using this new user after you have initially logged in using TEST user
Hope this helps
Ashwin N.

How to uninstall/remove security update for SQL Server 2012

My requirement is to uninstall/remove security update for SQL
Server 2012 Service Pack 1 only. so are these below steps are correct or do I need to take any extra precaution for uninstallation?
Go to Control panelàProgramsà
Programs and FeaturesàInstalled Updrtes, right click on update and uninstall
As per my knowledge in SQL Server 2005, we cannot uninstall a service pack. we have to uninstall SQL Server 2005 completely, and reinstall SQL Server 2005 with previous service
packs and updates. but Starting SQL Server 2008, we can uninstall a service pack using Control Panel.
Rahul

http://blogs.msdn.com/b/askjay/archive/2011/02/07/uninstalling-a-sql-server-service-pack.aspx
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

SQL*PLUS - remove output 'PL/SQL procedure successfully completed.'

Hi,
When I use SQL*PLUS to call a PLSQL procedure, it will always output text: 'PL/SQL procedure successfully completed.' when the PLSQL procedure completes.
I have a requirement to not display this message output. In SQL*PLUS how do you turn this off?

how to disable procedure successfully completed message in SQL*Plus

Got SQL *Plus query output in more than one in a single page

Hi All,
I have write a SQL *Plus code for execute one SQL query and registered as concurrent program. But I have got the output more than once in a single page after running the concurrent program. I am not getting what is the my code problem. Please can any one help me.
This is my SQL code.
-- These commands are added by applications concurrent manager
SET TERMOUT OFF
SET PAUSE OFF
SET HEADING OFF
SET FEEDBACK OFF
SET VERIFY OFF
SET ECHO OFF
WHENEVER sqlerror exit failure
-- set user environment
SET pagesize 999
SET linesize 860
SET appinfo on
SET tab off
SET newpage none
SET heading on
--SET colsep ','
-- define heading/footer
--ttitle -
-- left currdate -
-- center 'SSFT Open PO Report' -
-- right 'Page : ' format 999 sql.pno -
-- skip 1 -
-- center 'Organization US / Type Contract Labor / Status - Open' -
-- skip 2
--btitle -
-- skip 1 -
-- center 'Scansoft Inc. - All information confidential'
-- define columns
CLEAR columns
SET heading on
COLUMN c1 format a30 heading '"Last Name"' trunc
COLUMN c2 format a30 heading '"First Name"' trunc
COLUMN c3 format a50 heading '"Employee Name"' trunc
COLUMN c4 format a20 heading '"Timecard Number"' trunc
COLUMN c5 format a40 heading '"Expenditure Batch"' trunc
COLUMN c6 format a24 heading '"Weekending Date"' trunc
COLUMN c7 format a24 heading '"Expenditure Item Date"' trunc
COLUMN c8 format a20 heading '"Expendtrmonth"' trunc
COLUMN c9 format a20 heading '"Expendtryear"' trunc
COLUMN c10 format a24 heading '"Sortdate"' trunc
COLUMN c11 format 999999999 heading '"Task Id"'
COLUMN c12 format a30 heading '"Task Name"' trunc
COLUMN c13 format a30 heading '"Task Number"' trunc
COLUMN c14 format a24 heading '"Closed Date"' trunc
COLUMN c15 format a30 heading '"Project Name"' trunc
COLUMN c16 format a30 heading '"Project Number"' trunc
COLUMN c17 format a30 heading '"Project Status Code"' trunc
COLUMN c18 format a30 heading '"Expenditure Type"' trunc
COLUMN c19 format a30 heading '"Expenditure Org Name"' trunc
COLUMN c20 format 999999999 heading '"Organization Id"'
COLUMN c21 format a50 heading '"Projmrg"' trunc
COLUMN c22 format a25 heading '"Role"' trunc
COLUMN c23 format a24 heading '"Projmrg Start Date"' trunc
COLUMN c24 format a24 heading '"Projmrg Start Date"' trunc
COLUMN c25 format a35 heading '"Job Name"' trunc
COLUMN c26 format a35 heading '"Project Type"' trunc
COLUMN c27 format 999999999.99 heading '"Quentity"' trunc
-- define breaks & computes
--break -
-- on report skip 2 -
-- on c30 -
-- on c20 skip 1
--compute avg label 'Average' of c210 on report
-- select statement here
SELECT papf.last_name || '' c1, papf.first_name || '' c2,
papf.full_name || '' c3, pea.orig_user_exp_txn_reference || '' c4,
pea.expenditure_group || '' c5, pea.expenditure_ending_date || '' c6,
peia.expenditure_item_date || '' c7,
SUBSTR (TO_CHAR (peia.expenditure_item_date), 4, 3) || '' c8,
SUBSTR (TO_CHAR (peia.expenditure_item_date), 8, 2) || '' c9,
TO_DATE (SUBSTR (TO_CHAR (peia.expenditure_item_date), 4, 6),
'MM/YY'
|| '' c10,
peia.task_id || '' c11, pt.task_name || '' c12,
pt.task_number || '' c13, ppa.closed_date || '' c14, ppa.NAME || '' c15,
ppa.segment1 || '' c16, ppa.project_status_code || '' c17,
pet.expenditure_type || '' c18, haou.NAME || '' c19,
haou.organization_id || '' c20, pppv.full_name || '' c21,
pppv.ROLE || '' c22, pppv.start_date_active || '' c23,
pppv.end_date_active || '' c24, pj.NAME || '' c25,
ppa.project_type || '' c26, peia.quantity || '' c27
FROM pa.pa_expenditures_all pea,
pa.pa_expenditure_items_all peia,
pa.pa_tasks pt,
pa.pa_projects_all ppa,
hr.per_all_people_f papf,
hr.hr_all_organization_units haou,
pa.pa_expenditure_types pet,
apps.pa_project_players_v pppv,
hr.per_jobs pj
WHERE pea.expenditure_id = peia.expenditure_id
AND peia.task_id = pt.task_id
AND peia.job_id = pj.job_id
AND pt.project_id = ppa.project_id
AND pea.incurred_by_person_id = papf.person_id
AND pea.incurred_by_organization_id = haou.organization_id
AND pet.expenditure_type = peia.expenditure_type
AND ppa.project_id = pppv.project_id
AND pppv.end_date_active IS NULL
AND pea.expenditure_ending_date >= SUBSTR (SYSDATE - 545, 1, 9)
ORDER BY papf.full_name ASC,
pea.expenditure_ending_date ASC,
peia.expenditure_item_date ASC;
--spool off
Thanks in advance
--Subhas

Hi
Either remove the semicolon (;) or the slash (/) at the end of your query, as both will execute it.

Maximum length of SQL*Plus Command?

I'm typing a long query into SQL*Plus (Linux, version 9.2.0.1... yes, I know it's ancient).
If I run this query, all works fine:
select 'update myauditing_table set test_details='''||grantee||''' where myaudit_refno=''A.FE'';' from (select case when upper(value) in ('DBO','TRUE') then (select agg_concat(grantee) from dba_tab_privs where table_name='AUD$')
else (select 'AUDIT_TRAIL is set to: '||value from dual) end as grantee from v$parameter where upper(name)='AUDIT_TRAIL' order by grantee);
'UPDATEMYAUDITING_TABLESETTEST_DETAILS='''||GRANTEE||'''WHEREMYAUDIT_REFNO=''A.F
update myauditing_table set test_details='AUDIT_TRAIL is set to: DB' where myaud
it_refno='A.FE';(In other words, is SQL that generates other SQL: if AUDIT_TRAIL is set to something interesting, tell me who has access to the AUD$ table. And it's working fine... the agg_concat function mentioned is simply Tom Kyte's stragg function under another name, as lifted word-for-word from http://www.sqlsnippets.com/en/topic-11591.html)
Now this is what happens if I take out the linebreak after the mention of AUD$, so that the command is submitted as one single line of code:
SQL> select 'update myauditing_table set test_details='''||grantee||''' where myaudit_refno=''A.FE'';' from (select case when upper(value) in ('DBO','TRUE') then (select agg_concat(grantee) from dba_tab_privs where table_name='AUD$') else (select 'AUDIT_TRAIL is set to: '||value from dual) end as grantee from v$parameter where upper(name)='AUDIT_TRAIL' order by grantee);
SP2-0734: unknown command beginning "s set to: ..." - rest of line ignored.The error message indicates that the text has been 'split' at the 'AUDIT_TRAIL is set to...' bit, so that "s set to" is being treated as a new command, which is of course syntactically invalid. There is definitely no other change in text between the two versions, apart from the removal of a carriage return before the "else" statement.
Possibly a coincidence, but the first "s" in "s set to" appears at position 258 in the entire text... close to a possible 255 or 256 character limit, perhaps?
The same problem happens whether I run the command as a script (@mysql.sql) or typed in directly into a client SQL*Plus session. Is there some inherent limit to the length of commands that SQL*Plus can process in this version? My code runs fine on 10g and 11g databases/clients, whether it's on one line or two. Anyone know of a bug in 9i regarding this? And if there's a workaround (other than the obvious one of upgrading, of course!)

As mentioned, it's choking at the 258th character, not the 240th. Also, it's a SELECT statement, not a COPY command (one relates to the database, the other is an internal SQL*Plus feature). And someone else also kindly pointed out that SQL*Plus has a command limit length (i.e., database-related commands) of 2500 characters. So I don't think that's the issue.
I can be a bit more specific about this one now, though. I've a sequence of Solaris boxes running 9.2.0.1 up, and the results are that 9.2.0.1 is affected; and it's a problem for 9.2.0.7:
SQL> select * from v$version;
BANNER
Oracle9i Enterprise Edition Release 9.2.0.1.0 - 64bit Production
PL/SQL Release 9.2.0.1.0 - Production
CORE 9.2.0.1.0 Production
TNS for Solaris: Version 9.2.0.1.0 - Production
NLSRTL Version 9.2.0.1.0 - Production
SQL> select 'update myauditing_table set test_details='''||grantee||''' where myaudit_refno=''A.FE'';' from (select case when upper(value) in ('DBO','TRUE') then (select agg_concat(grantee) from dba_tab_privs where table_name='AUD$') else (select 'AUDIT_TRAIL is set to: '||value from dual) end as grantee from v$parameter where upper(name)='AUDIT_TRAIL' order by grantee);
SP2-0734: unknown command beginning "s set to: ..." - rest of line ignored.And...
SQL> select * from v$version;
BANNER
Oracle9i Enterprise Edition Release 9.2.0.7.0 - 64bit Production
PL/SQL Release 9.2.0.7.0 - Production
CORE 9.2.0.7.0 Production
TNS for Solaris: Version 9.2.0.7.0 - Production
NLSRTL Version 9.2.0.7.0 - Production
SQL> select 'update myauditing_table set test_details='''||grantee||''' where myaudit_refno=''A.FE'';' from (select case when upper(value) in ('DBO','TRUE') then (select agg_concat(grantee) from dba_tab_privs where table_name='AUD$') else (select 'AUDIT_TRAIL is set to: '||value from dual) end as grantee from v$parameter where upper(name)='AUDIT_TRAIL' order by grantee);
SP2-0734: unknown command beginning "s set to: ..." - rest of line ignored.But in 10.2.0.1, the problem disappears.
I am not sure, but it is perhaps related to metalink note 285913.1, since we did get some ORA-00600: internal error code, arguments: [qernsRowP], [1] errors in the alert log with a slightly different version of the above query. Changing the query obviously alters the test, though, so it may be completely unrelated.
Either way, I think it's definitely a version-specific SQL*Plus bug (though it would be nice if any other 9i owners out there could try it and report back!)
Anyway, the workaround is simply to submit the command on two separate lines, wherever possible. And of course... to upgrade.

Connect via SQL*Plus taking more time in Oracle 11 than in 10

Oracle Version
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
PL/SQL Release 11.2.0.3.0 - Production
CORE 11.2.0.3.0 Production
TNS for IBM/AIX RISC System/6000: Version 11.2.0.3.0 - Production
NLSRTL Version 11.2.0.3.0 - Productioncurrently migrating from
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
CORE 10.2.0.4.0 Production
TNS for IBM/AIX RISC System/6000: Version 10.2.0.4.0 - Productio
NLSRTL Version 10.2.0.4.0 - ProductionOS is AIX 5.3 for Oracle 10 and AIX 6.1 for Oracle 11.
We are currently in the process of migrating some applications from Oracle 10 to 11. Our admins have setup a new development system for us with an Oracle 11 instance. Regarding performance the new system behaves more or less the same than our old, e.g. when executing SQLs we notice hardly any performance differences and those we find are slightly in favour of the new system.
But now we discovered that the time it takes to establish a database connection via SQL*Plus is longer on the Oracle 11 system. Running the following code
sqlplus -s user/pw@database <<END
quit
ENDa thousand times takes ~60s under Oracle 10 but ~140s under Oracle 11. This may not seem much but we are running a test framework consisting of a bunch of shell scripts where several thousand connections are openend via SQL*Plus to execute some SQLs, so that even this small time difference results in rather huge difference in total runtime. The SQLs themself require roughly the same time in both databases, as already mentioned above they are in fact slightly faster in Oracle 11.
To analyze the time difference I ran a trace for the connect with the following parameters in sqlnet.ora
TRACE_LEVEL_CLIENT=4
TRACE_UNIQUE_CLIENT=ONand found out that there is a time difference of about 70ms during the connect handshake:
Oracle 10
[22-MAR-2013 12:13:09:595] nscon: doing connect handshake...
[22-MAR-2013 12:13:09:595] nscon: sending NSPTCN packet
[22-MAR-2013 12:13:09:621] nscon: got NSPTRS packet
[22-MAR-2013 12:13:09:621] nscon: sending NSPTCN packetOracle 11
(1) [22-MAR-2013 12:15:26:812] nscon: doing connect handshake...
(1) [22-MAR-2013 12:15:26:812] nscon: sending NSPTCN packet
(1) [22-MAR-2013 12:15:26:906] nscon: got NSPTRS packet
(1) [22-MAR-2013 12:15:26:906] nscon: sending NSPTCN packetUnder Oracle 10 there are 26ms between sending the NSPTCN packet and getting the NSPTRS packet, whereas under Oracle 11 this takes 94ms. I ran the trace again, this time with
TRACE_LEVEL_CLIENT=16and got the following results for the critical interval:
Oracle 10:
[22-MAR-2013 13:17:37:638] nscon: sending NSPTCN packet
[22-MAR-2013 13:17:37:638] nspsend: entry
[22-MAR-2013 13:17:37:638] nspsend: plen=218, type=1
[22-MAR-2013 13:17:37:638] nttwr: entry
[22-MAR-2013 13:17:37:638] nttwr: socket 9 had bytes written=218
[22-MAR-2013 13:17:37:638] nttwr: exit
[22-MAR-2013 13:17:37:638] nspsend: packet dump
<<packet dump removed>>
[22-MAR-2013 13:17:37:638] nspsend: 218 bytes to transport
[22-MAR-2013 13:17:37:638] nspsend: normal exit
[22-MAR-2013 13:17:37:638] nscon: exit (0)
[22-MAR-2013 13:17:37:638] nsdo: nsctxrnk=0
[22-MAR-2013 13:17:37:638] nsdo: normal exit
[22-MAR-2013 13:17:37:638] nsdo: entry
[22-MAR-2013 13:17:37:638] nsdo: cid=0, opcode=68, *bl=512, *what=9, uflgs=0x0, cflgs=0x3
[22-MAR-2013 13:17:37:638] nsdo: rank=64, nsctxrnk=0
[22-MAR-2013 13:17:37:638] nsdo: nsctx: state=2, flg=0x4005, mvd=0
[22-MAR-2013 13:17:37:638] nsdo: gtn=10, gtc=10, ptn=10, ptc=2011
[22-MAR-2013 13:17:37:638] nscon: entry
[22-MAR-2013 13:17:37:638] nscon: recving a packet
[22-MAR-2013 13:17:37:638] nsprecv: entry
[22-MAR-2013 13:17:37:638] nsprecv: reading from transport...
[22-MAR-2013 13:17:37:638] nttrd: entry
[22-MAR-2013 13:17:37:665] nttrd: socket 9 had bytes read=8
[22-MAR-2013 13:17:37:665] nttrd: exit
[22-MAR-2013 13:17:37:665] nsprecv: 8 bytes from transport
[22-MAR-2013 13:17:37:665] nsprecv: tlen=8, plen=8, type=11
[22-MAR-2013 13:17:37:665] nsprecv: packet dump
[22-MAR-2013 13:17:37:665] nsprecv: 00 08 00 00 0B 00 00 00 |........|
[22-MAR-2013 13:17:37:665] nsprecv: normal exit
[22-MAR-2013 13:17:37:665] nscon: got NSPTRS packetOracle 11
(1) [22-MAR-2013 13:33:40:504] nscon: sending NSPTCN packet
(1) [22-MAR-2013 13:33:40:504] nspsend: entry
(1) [22-MAR-2013 13:33:40:504] nspsend: plen=205, type=1
(1) [22-MAR-2013 13:33:40:504] nttwr: entry
(1) [22-MAR-2013 13:33:40:504] nttwr: socket 8 had bytes written=205
(1) [22-MAR-2013 13:33:40:504] nttwr: exit
(1) [22-MAR-2013 13:33:40:504] nspsend: packet dump
<<packet dump removed>>
(1) [22-MAR-2013 13:33:40:505] nspsend: 205 bytes to transport
(1) [22-MAR-2013 13:33:40:505] nspsend: normal exit
(1) [22-MAR-2013 13:33:40:505] nscon: exit (0)
(1) [22-MAR-2013 13:33:40:505] snsbitts_ts: entry
(1) [22-MAR-2013 13:33:40:505] snsbitts_ts: acquired the bit
(1) [22-MAR-2013 13:33:40:505] snsbitts_ts: normal exit
(1) [22-MAR-2013 13:33:40:505] nsdo: nsctxrnk=0
(1) [22-MAR-2013 13:33:40:505] snsbitcl_ts: entry
(1) [22-MAR-2013 13:33:40:505] snsbitcl_ts: normal exit
(1) [22-MAR-2013 13:33:40:505] nsdo: normal exit
(1) [22-MAR-2013 13:33:40:505] nsdo: entry
(1) [22-MAR-2013 13:33:40:505] nsdo: cid=0, opcode=68, *bl=2048, *what=9, uflgs=0x0, cflgs=0x3
(1) [22-MAR-2013 13:33:40:505] snsbitts_ts: entry
(1) [22-MAR-2013 13:33:40:505] snsbitts_ts: acquired the bit
(1) [22-MAR-2013 13:33:40:505] snsbitts_ts: normal exit
(1) [22-MAR-2013 13:33:40:505] nsdo: rank=64, nsctxrnk=0
(1) [22-MAR-2013 13:33:40:505] snsbitcl_ts: entry
(1) [22-MAR-2013 13:33:40:505] snsbitcl_ts: normal exit
(1) [22-MAR-2013 13:33:40:505] nsdo: nsctx: state=2, flg=0x4005, mvd=0
(1) [22-MAR-2013 13:33:40:505] nsdo: gtn=10, gtc=10, ptn=10, ptc=8155
(1) [22-MAR-2013 13:33:40:505] nscon: entry
(1) [22-MAR-2013 13:33:40:505] nscon: recving a packet
(1) [22-MAR-2013 13:33:40:505] nsprecv: entry
(1) [22-MAR-2013 13:33:40:505] nsprecv: reading from transport...
(1) [22-MAR-2013 13:33:40:505] nttrd: entry
(1) [22-MAR-2013 13:33:40:618] nttrd: socket 8 had bytes read=8
(1) [22-MAR-2013 13:33:40:618] nttrd: exit
(1) [22-MAR-2013 13:33:40:618] nsprecv: 8 bytes from transport
(1) [22-MAR-2013 13:33:40:618] nsprecv: tlen=8, plen=8, type=11
(1) [22-MAR-2013 13:33:40:618] nsprecv: packet dump
(1) [22-MAR-2013 13:33:40:618] nsprecv: 00 08 00 00 0B 00 00 00 |........|
(1) [22-MAR-2013 13:33:40:618] nsprecv: normal exit
(1) [22-MAR-2013 13:33:40:618] nscon: got NSPTRS packetAny ideas what could be the reason for this time difference? Something in our network configuration or something else?

With local connections - I do not think a TCP packet send from an IP to the same IP, leaves the interface as an actual wire protocol/signal. If I'm correct, then running local connection tests will be mostly useless in checking the actual network infrastructure.
Tests 3 and 4 should be showing the same connection times as the same physical network infrastructure is used - only the direction is reversed in the tests.
I would assume that port settings on the switches and interface settings on the routers treat packets equally in both directions between 2 servers. But this could in part explain the problem if this is not the case. In a case of a router for example, the 1st test's ingress interface is the egress interface of the 2nd test (and vice versa). Configurations can differ substantially between interfaces on the same router. Likewise if there is a firewall - as different rule sets are applied in each test and these rule sets could differ.
So I would not be too quick to state that this is definitely not a network problem. But I agree that based on the small percentage difference (assuming comparable tests), it does not look like a network issue.
The next step is to determine what the delay is between the listener accepting the client connection, and the connection being serviced by a dedicated server process.
This will require listener tracing - tracing the time from when the listener accepted the connection (and parsed the TNS connection string), to handing off the connection to the dedicated server process.
As a comparison test, you can also test shared server connections. Dispatcher processes (of the db instance) register themselves with the listener. The shared server client hand off is thus done to an existing server process - no need for the Listener to make a kernel call to load and initialise an executable image.
Shared connections are typically faster than dedicated connections in this respect.
If there is a major time difference, then it means some kind of issue with the listener dealing with dedicated servers as oppose to dispatcher hand off's. As both connections would have had very similar network transit time - which means the connection time difference is related directly to dealing with a dedicated server connection request and hand off.
You can also substitute the oracle executable with a wrapper - and troubleshoot the actual dedicated server startup. I've only done this with Oracle XE 10.2 though and with local IPC connections. Unsure how robust this will be for testing purposes via TCP using 11g.

TNSPING failure and but surprising connecting through SQL*PLUS

I have Oracle 9i and Oracle 10g express edition installed on my local machine.But since in the path i specified path of Oracle10g first so always tnsnames.ora got picked up from Oracl10g directory which is
C:\softwares\oraclexe\app\oracle\product\10.2.0\server\network\admin\sqlnet.ora
Following are the contents of my sqlnet.ora :--->
SQLNET.AUTHENTICATION_SERVICES = (NTS)
Following are the contents of my tnsnames.ora:-->
CCTD91 =(DESCRIPTION =
(ADDRESS_LIST =(ADDRESS = (PROTOCOL = TCP)(HOST = cctdev91.jankoc.com)(PORT = 1521)))(CONNECT_DATA =(SERVICE_NAME = CCTD91)))
Now when i am doing tnsping to this i got the error as:
C:\>tnsping cctd91
TNS Ping Utility for 32-bit Windows: Version 10.2.0.1.0 - Production on 23-APR-2011 16:08:52
Copyright (c) 1997, 2005, Oracle. All rights reserved.
Used parameter files:
C:\softwares\oraclexe\app\oracle\product\10.2.0\server\network\admin\sqlnet.ora
TNS-03505: Failed to resolve name
But when i connect through Oracle 9i client(SQL*Plus) like peter/devworks@CCTD91, then i am able to connect successfully to Oracle 11g.
Could someone let me know why TNSPING is failing for this and then still why i am able to connect thru SQL*PLUS using the name defined in TNSNAMES.ORA. ?

sqlnet.ora is having just one line:
SQLNET.AUTHENTICATION_SERVICES = (NTS)
I tried by adding another line: NAMES.DIRECTORY_PATH=(TNSNAMES) but did not make any difference so i removed.
C:\>lsnrctl service
LSNRCTL for 32-bit Windows: Version 10.2.0.1.0 - Production on 24-APR-2011 19:06:36
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC_FOR_XE)))
Services Summary...
Service "CLRExtProc" has 1 instance(s).
Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0
LOCAL SERVER
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0
LOCAL SERVER
Service "XEXDB" has 1 instance(s).
Instance "xe", status READY, has 1 handler(s) for this service...
Handler(s):
"D000" established:0 refused:0 current:0 max:1002 state:ready
DISPATCHER <machine: localhost, pid: 3288>
(ADDRESS=(PROTOCOL=tcp)(HOST=localhost.XXX.XXX.COM)(PORT=1041))
Service "XE_XPT" has 1 instance(s).
Instance "xe", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0 state:ready
LOCAL SERVER
Service "xe" has 1 instance(s).
Instance "xe", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0 state:ready
LOCAL SERVER
The command completed successfully
C:\>lsnrctl status
LSNRCTL for 32-bit Windows: Version 10.2.0.1.0 - Production on 24-APR-2011 19:08:48
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC_FOR_XE)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for 32-bit Windows: Version 10.2.0.1.0 - Production
Start Date 23-APR-2011 16:05:49
Uptime 1 days 3 hr. 2 min. 59 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Default Service XE
Listener Parameter File C:\softwares\oraclexe\app\oracle\product\10.2.0\server\network\admin\listener.ora
Listener Log File C:\softwares\oraclexe\app\oracle\product\10.2.0\server\network\log\listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC_FOR_XEipc)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost.xxx.xxx.COM)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=8080))(Presentation=HTTP)(Session=RAW))
Services Summary...
Service "CLRExtProc" has 1 instance(s).
Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "XEXDB" has 1 instance(s).
Instance "xe", status READY, has 1 handler(s) for this service...
Service "XE_XPT" has 1 instance(s).
Instance "xe", status READY, has 1 handler(s) for this service...
Service "xe" has 1 instance(s).
Instance "xe", status READY, has 1 handler(s) for this service...
The command completed successfully
C:\>
Oracle 11g is installed remotely on our office LAN.
Please note that i just removed company name with XXX from the above lsnrcts commands output, just for security reasons.

Seek help to format spool file from SQL*PLUS

I am running a Unix shell script to call a Oracle 11g SQL script from a Oracle database. In this SQL script, I need to connect to many different remote databases to select data, then sool these records as one big text file to a directory. Then email the file to related Group users. In the spool file, there is a line on the top of each page like this:
DUMMY
DB_NAME
I know this is caused by connect to remote database in SQL*PLUS. My connection string is like this:
Conn system/password@Oracle_SID
How can I remove these lines or how to skip these lines into spool file? Please advise. Thanks in advnce. Wish all of you Happy New Year!!!

Hi,
It sounds like you have some kind of formatting (such as SQL*Plus TTITLE) producing the output you don't want. If that's the case, temporarily stopping the spooling might not help you. Find out what is causing the output that you don't want. You say that you know it is caused by the CONNECT statements, but it must be more than that. I've written scripts with CONNECT statements that don't have anything like what you reported at the top of each page; in fact, they don't even have pages: the output is one continuous stream. Find out what's putting the unwanted output there, and that will be a big clue as to how you can stop it.
You say that you know the unwanted titles are there because of the CONNECT statements. If so, use database links instead of CONNECT. You don't have to use dbms_scheduler or utl_file; just eliminate the CONNECT statements. (I'm not saying that there's anything wrong with dbms_scheduler or utl_file; you should definitely investigate those tools. I'm just saying that using database links is independent of them.)
What would happen if you did all your connecting to different databases at the OS level? Can you write a shell script that connects to each database in turn, and runs a SQL*Plus script in each one. Each SQL*Plus script would have a SPOOL or SPOOL ... APPEND command, or maybe you could build the SPOOL into a LOGIN.SQL script.

8.1.7: ORA-01410 in PL/SQL but not SQL*Plus

This has been driving me crazy, and a search here and in comp.databases.oracle didn't turn up any solutions.
When the following code is part of a stored procedure, it fails with ORA-01410 (Invalid ROWID). It executes perfectly from SQL*Plus, I've verified that TMP_TASK_DATA contains data, and the query clearly specifies a ROWID.
As noted in the subject, this occurs on 8.1.7. TMP_TASK_DATA and TMP_TASK_RETRIEVAL are both global temp tables. I don't currently have access to Metalink, so was hoping that someone has run across this and has some hints.
Thx,
(query edited to limit "IN" list):
        INSERT INTO TMP_TASK_RETRIEVAL
                (TASK_ID, TD_ROWID, SORT_ORDER)
        SELECT TASK_ID, TD_ROWID, ROWNUM
        FROM    (
                SELECT TASK_ID, TD_ROWID
                FROM    (
                        SELECT TASK_ID,
                                ROWID                                   as TD_ROWID,
                                SF_GET_PRIORITY(TASK_TYPE, 1 )          as PRIORITY_COMM,
                                COMPLETED_TIME                          as FINISH_TIME,
                                FIRST_READY_TIME                        as QUEUE_TIME
                        FROM    TMP_TASK_DATA
                        WHERE   USER_NUMBER = v_USER_NUM
                        AND     TASK_TYPE in
                                'AAAA', 'BBBB', 'CCCC'
                ORDER BY
                        PRIORITY_COMM,
                        decode(PRIORITY_COMM, 10, FINISH_TIME, QUEUE_TIME)
                );

Thanks for the info. It turned out that I was wrong about removing the PL/SQL variable from the query; either that, or the error occurs at arbitrary times.
As best I can tell, a ROWID simply can't be passed between nested inline views, so I reduced them to one level (which means that I have to run the function twice in the ORDER BY, rather than once in the nested select).

SQL*Plus variable assignment works for 8i but not 9i

We have scripts that connect to each database on the box and perform database tasks nightly. The scripts first set the environment then connects to each database with SQL*Plus. This works for 8i but fails in the recently created 9i environment. (Unix Solaris environment)
Because the SQL*Plus connection appears in many areas in the scripts, we assign the following connection string to a variable:
SQLPLUS="/usr/oracle/product/9.2.0/bin/sqlplus -s 'xxx/xxxxxx@xxxx as sysdba'"
Export SQLPLUS
echo "$SQLPLUS"
(This echo out correctly: /usr/oracle/product/9.2.0/bin/sqlplus -s 'xxx/xxxxxx@xxxx as sysdba')
It fails when the script calls the assigned variable:
$SQLPLUS <<-EOF
with the following error:
Usage: SQLPLUS [ [<option>] [<logon>] [<start>] ]
where <option> ::= -H | -V | [ [-L] [-M <o>] [-R <n>] [-S] ]
<logon> ::= <username>[<password>][@<connect_string>] | / | /NOLOG
<start> ::= @<URI>|<filename>[.<ext>] [<parameter> ...]
"-H" displays the SQL*Plus version banner and usage syntax
"-V" displays the SQL*Plus version banner
"-L" attempts log on just once
"-M <o>" uses HTML markup options <o>
"-R <n>" uses restricted mode <n>
"-S" uses silent mode
However, if I remove the SQLPLUS variable assignment and changed all occurrence of
$SQLPLUS <<-EOF to
/usr/oracle/product/9.2.0/bin/sqlplus -s 'xxx/xxxxxx@xxxx as sysdba' <<-EOF
Then the script runs successfully. But this solution is cumbersome.
Any ideas as to how to have the script work with assigning the SQLPLUS variable????
Any help is appreciated.

I has an immediate suspicion it might be related to the issue
mentioned in
http://otn.oracle.com/support/tech/sql_plus/htdocs/sub_var2.html#2_7
but this proved wrong: the SP2-306 still occurs in the latest
SQL*Plus.
I wonder what version of 8i you had working? With an old SQL*Plus
8.1.7.0 my connection failed the same as in 9.2 and 10i.
My solution was to do:
SQLPLUS='sqlplus -s'
UNPW='/ as sysdba'
$SQLPLUS "$UNPW" <<EOF
EOFThis worked in 9.2.0.5, 10.1.0.2 and 8.1.7.0.
One common security risk on UNIX remains: putting the username and
password on the command line. On some systems a "ps" command will
show the password to any user. If OS authentication cannot be used
for connection, perhaps putting the username/password in the SQL
script may be more secure?
A final note is that in SQL*Plus 10g, no quotes are needed around
AS SYSDBA, i.e.
sqlplus / as sysdba works from the OS prompt, whereas in 9.2 you need to do
sqlplus "/ as sysdba"This makes a solution easy:
SQLPLUS="/usr/oracle/product/10.1.0/bin/sqlplus -s xxx/xxxxxx@xxxx as sysdba"-- CJ

SQL*Plus assignment works for 8i but not 9i

We have scripts that connect to each database on the box and perform database tasks nightly. The scripts first set the environment then connects to each database with SQL*Plus. This works for 8i but fails in the recently created 9i environment.
Because the SQL*Plus connection appears in many areas in the scripts, we assign the following connection string to a variable:
SQLPLUS="/usr/oracle/product/9.2.0/bin/sqlplus -s 'xxx/xxxxxx@xxxx as sysdba'"
Export SQLPLUS
echo "$SQLPLUS"
(This echo out correctly: /usr/oracle/product/9.2.0/bin/sqlplus -s 'xxx/xxxxxx@xxxx as sysdba')
It fails when the script calls the assigned variable:
$SQLPLUS <<-EOF
with the following error:
Usage: SQLPLUS [ [<option>] [<logon>] [<start>] ]
where <option> ::= -H | -V | [ [-L] [-M <o>] [-R <n>] [-S] ]
<logon> ::= <username>[<password>][@<connect_string>] | / | /NOLOG
<start> ::= @<URI>|<filename>[.<ext>] [<parameter> ...]
"-H" displays the SQL*Plus version banner and usage syntax
"-V" displays the SQL*Plus version banner
"-L" attempts log on just once
"-M <o>" uses HTML markup options <o>
"-R <n>" uses restricted mode <n>
"-S" uses silent mode
However, if I remove the SQLPLUS variable assignment and changed all occurrence of
$SQLPLUS <<-EOF to
/usr/oracle/product/9.2.0/bin/sqlplus -s 'xxx/xxxxxx@xxxx as sysdba' <<-EOF
Then the script runs successfully. But this solution is cumbersome.
Any ideas as to how to have the script work with assigning the SQLPLUS variable????
Any help is appreciated

I has an immediate suspicion it might be related to the issue
mentioned in
http://otn.oracle.com/support/tech/sql_plus/htdocs/sub_var2.html#2_7
but this proved wrong: the SP2-306 still occurs in the latest
SQL*Plus.
I wonder what version of 8i you had working? With an old SQL*Plus
8.1.7.0 my connection failed the same as in 9.2 and 10i.
My solution was to do:
SQLPLUS='sqlplus -s'
UNPW='/ as sysdba'
$SQLPLUS "$UNPW" <<EOF
EOFThis worked in 9.2.0.5, 10.1.0.2 and 8.1.7.0.
One common security risk on UNIX remains: putting the username and
password on the command line. On some systems a "ps" command will
show the password to any user. If OS authentication cannot be used
for connection, perhaps putting the username/password in the SQL
script may be more secure?
A final note is that in SQL*Plus 10g, no quotes are needed around
AS SYSDBA, i.e.
sqlplus / as sysdba works from the OS prompt, whereas in 9.2 you need to do
sqlplus "/ as sysdba"This makes a solution easy:
SQLPLUS="/usr/oracle/product/10.1.0/bin/sqlplus -s xxx/xxxxxx@xxxx as sysdba"-- CJ

SQL*Plus: Release 10.1.0.4.0 startup behaviour (glogin and login)

Hi,
I'm working in a unix environment where I have a lot of sql scripts to run using different DB users but only one OS user.
I notice that in this version of SQL*Plus something was change regarding glogin and login scripts: they are executed also after a successful connect. There is no warning in the documentation to NOT use CONNECT in these scripts.
What happens is recurrent execution of the same login script if there is a CONNECT command in it up to 20 time (the limit of recurrence in SQL*Plus). The only workaround I found is to put SET SQLPLUSCOMPATIBILITY to a prior version in the same login file before the CONNECT command.
Has anyone a better idea ?
Thank you.

There is no warning in the documentation to NOT use CONNECT in these scripts.the change is documented
http://download.oracle.com/docs/cd/B19306_01/server.102/b14357/ch12015.htm
When you run a CONNECT command, the site profile, glogin.sql, and the user profile, login.sql, are executed.
I understand your problem. The best would be to use a valid login and glogin script. I do not recommend big modification in glogin.
Some tools, like OEMGC, particulary hates aggressive staff in glogin.sql, for example ALTER SESSION, etc...
It is not recommended to do a "SET TERMOUT OFF" or a "WHENEVER SQLERROR CONTINUE" or any DML/DDL in your glogin, because it will irreversibily affect some scripts.
The best I can rate you : remove your fancy staff from glogin.sql. If it is about the sql prompt, use 10g feature, like
set SQLP _USER@""_CONNECT_IDENTIFIER>much better than selecting from global name!!!
HTH
Laurent

SQL Devloper working fine but not SQL Plus

Hi,
I am facing a problem that I can connect to oracle server via SQL Developer but cannot connect to the same using SQL*Plus.
ORA-12154: TNS:could not resolve service name
I checked many forums and followed each advices but in vein. To make sure that I have got only one instance of tnsnames.ora file, I removed oracle completely from my system and did the fresh installation of the same.Again, SQL Developer worked but not SQL*Plus.
Also, I updated dummy value in the tnsnames.ora file to check if SQLDeveloper is pointing to correct ora file, it failed means that its pointing to correct one only.
Also, this is not the problem with single machine rather my colleague is also facing the same problem while connecting to the same oracle. It suggest me that its rather problem with server side then client one but what do you people think the actual problem can be.
Kindly advice
I am using oracle 10.2 and OS window server 2003 standard edition.
Cheers,
D
Edited by: user9022426 on 20-Jan-2010 14:25

The problem is client side.
The error message means that you're not getting
Are you using a TNS connection for SQL Developer?
If so, this error suggests that SQL Developer and SQL*Plus are not going through the same ORACLE_HOME and/or TNSNAMES.ORA.
For example, do you have the environment variable TNS_ADMIN set?
If you have metalink access, then there is a troubleshooting guide for ORA-12154 in Metalink note 114085.1

SQL Plus doesn't RPAD

Hi All,
I'm running into a peculiar problem where I'm trying to pool an oracle table that has about 30 million records into a text file. I'm using Toad for Oracle version 10.5. When I spool my results, I'm rpading a column to 54 characters with blank spaces. When I run this spool as a script in Toad or using Toad's Quest Script Runner it pads it no problem but when I try doing it through the "Execute SQL via SQL Plus" command in Toad it doesn't do the rpading. I don't get it. Anyway, here's the script...just removed the name of my table and column names and replaced them with more generic names:
Spool on
set heading off
SET PAGESIZE 0
SET TRIMSPOOL ON
SET LINESIZE 100
set feedback off
set echo off
set termout off
Spool "C:\test.txt"
select
rpad(column1,54) as column1
from crg_input_final
where rownum <=100
order by
column2,
column1;
Spool off;
I always assumed that SQL is SQL...no matter if you run it in Toad or SQL Plus or wherever. Am I missing something?
Thanks

SET TRIMSPOOL ONthis will always remove trailing spaces from your spool file.
You could try:
set linesize 54
set trimspool off
spool "C:\test.txt"
select column1
from crg_input_final
where rownum <=100
order by
column2,
column1;
Spool off;if you need padding on the last column.

Uninstall/Remove Sql plus

Similar Messages

Maybe you are looking for