Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
vote44d
own
voteacc
epted
HA High Availability
HADR High Availability Disaster Recovery
HDD Hard Disk Drive
ICP Index Condition Pushdown (MySQL)
IOPS IO Per Second
IOT Index Organized Table (Oracle)
ISAM - Indexed Sequential Access Method
I/O Input/Output
JDBC Java Database Connectivity
KV Key/Value
LAMP - Linux, Apache, MySQL and PHP
LBAC - Label Based Access Control
LOB Large OBject
LPAR Logical Partition
LRU Last Recently Used (algorithm)
LUN Logical Unit Number
MDC Multidimensional Clustering Table
MDM Master Data Management
MDX Multidimensional Expressions
MED Management of External Data
MQT Materialized Query Table (IBM DB2)
MV Materialized View
MVCC Multiversion Concurrency Control
NAS - Network Attached Storage
NCI Non-clustered Index
NF - Normal Form (ie: 1NF, first normal form)
ODBC Open Database Connectivity
ODS - Operational Data Store
OLAP Online Analytical Processing
OLTP Online Transaction Processing
OODBMS Object-Oriented Database Management System
OOM Out Of Memory
ORM Object-Relational Mapping
OS Operating System
PK Primary Key
PL/pgSQL Procedural Language/SQL (PostgreSQL) used for
writing stored procedures. Similar to PL/SQL.
PL/SQL Procedural Language/SQL (Oracle) used for writing
stored procedures. Also see SQL PL.
QPS Queries Per Second
RAC Real Application Clusters (Oracle)
RAID Redundant Array of Independent Disks
RBAR Row By Agonizing Row
RDBMS Relational Database Management System
RBR Row-Based Replication (MySQL)
RPO - Recovery Point Objective - how much data you can afford to
lose. If your server went down, this is the point at which you'd be
able to recover the data.
RR Repeatable Read - an isolation level supported by different
database management systems.
RS
Read Stability - an isolation level supported by different
database management systems.
Replica Set - multiple physical nodes forming a logical node with
redundant data. Most commonly used in the MongoDB ecosystem
RTO - Recovery Time Objective - how much time it would take you
to recover the data to the RPO
SAN Storage Area Network
SBR Statement-Based Replication (MySQL)
SCD Slowly Changing Dimension
SE Storage Engine (MySQL and forks)
SEQUEL Structured English QUEry Language, which was IBM's
precursor to SQL, which is why SQL is sometimes (often?)
pronounced SEQUEL and not S.Q.L.
SP Stored Procedure
SQL Structured Query Language
SQL PL SQL Procedure Language used for writing stored
procedures. Also see PL/SQL.
SQL/XML an extension of the SQL language used for querying
XML.
SSD Solid State Drive
TPS* - Transactions Per Second, a measurement of database
performance.
UAT - User Acceptance Testing
UDF User Defined Function
UDT User Defined Type
UR Uncommitted Read - an isolation level supported by different
database management systems.
URLT - Update Resume; Leave Town - For those DBAs that don't
bother putting together a proper recovery strategy
XML eXtensible Markup Language
XSD XML Schema Definition
XSLT XML Stylesheet Transformation
share
community wiki
Chris Aldrich
Heres a list of 40+ Useful Oracle queries that every Oracle developer must
bookmark. These queries range from date manipulation, getting server info,
get execution status, calculate database size etc.
Date / Time related queries
1.
This query is similar to above but returns last day of current month. One
thing worth noting is that it automatically takes care of leap year. So if
you have 29 days in Feb, it will return 29/2. Also similar to above query
replace SYSDATE with any other date column/value to find last day of
that particular month.
SELECT TRUNC (LAST_DAY (SYSDATE)) "Last day of current month"
FROM DUAL;
3.
Get the first day of the Year
First day of year is always 1-Jan. This query can be use in stored
procedure where you quickly want first day of year for some calculation.
SELECT TRUNC (SYSDATE, 'YEAR') "Year First Day" FROM DUAL;
4.
Get the last day of the year
Similar to above query. Instead of first day this query returns last day of
current year.
SELECT ADD_MONTHS (TRUNC (SYSDATE, 'YEAR'), 12) - 1 "Year Last Day"
FROM DUAL
5.
Get number of days in current month
Now this is useful. This query returns number of days in current month.
You can change SYSDATE with any date/value to know number of days in
that month.
SELECT CAST (TO_CHAR (LAST_DAY (SYSDATE), 'dd') AS INT)
number_of_days
FROM DUAL;
6.
Get number of days left in current month
Below query calculates number of days left in current month.
SELECT SYSDATE,
LAST_DAY (SYSDATE) "Last",
LAST_DAY (SYSDATE) - SYSDATE "Days left"
FROM DUAL;
7.
Get number of days between two dates
Use this query to get difference between two dates in number of days.
Display each months start and end date upto last month of the year
This clever query displays start date and end date of each month in
current year. You might want to use this for certain types of calculations.
A simple query that can be used to check if a table exists before you
create it. This way you can make your create table script rerunnable. Just
replace table_name with actual table you want to check. This query will
check if table exists for current user (from where the query is executed).
SELECT table_name
FROM user_tables
WHERE table_name = 'TABLE_NAME';
16. Check if a column exists in a table
Simple query to check if a particular column exists in table. Useful when
you tries to add new column in table using ALTER TABLE statement, you
might wanna check if column already exists before adding one.
SELECT column_name AS FOUND
FROM user_tab_cols
WHERE table_name = 'TABLE_NAME' AND column_name =
'COLUMN_NAME';
17. Showing the table structure
This query gives you the DDL statement for any table. Notice we have
pass TABLE as first parameter. This query can be generalized to get DDL
statement of any database object. For example to get DDL for a view just
replace first argument with VIEW and second with your view name and
so.
SELECT DBMS_METADATA.get_ddl ('TABLE', 'TABLE_NAME', 'USER_NAME')
FROM DUAL;
18. Getting current schema
Yet another query to get current schema name.
SELECT SYS_CONTEXT ('userenv', 'current_schema') FROM DUAL;
19. Changing current schema
Yet another query to change the current schema. Useful when your script
is expected to run under certain user but is actually executed by other
user. It is always safe to set the current user to what your script expects.
ALTER SESSION SET CURRENT_SCHEMA = new_schema;
Database administration queries
20.
SELECT VALUE
FROM v$system_parameter
WHERE name = 'compatible';
Store data case sensitive but to index it case insensitive
Now this ones tricky. Sometime you might querying database on some
value independent of case. In your query you might do UPPER(..) =
UPPER(..) on both sides to make it case insensitive. Now in such cases,
you might want to make your index case insensitive so that they dont
occupy more space. Feel free to experiment with this one.
CREATE TABLE tab (col1 VARCHAR2 (10));
CREATE INDEX idx1
ON tab (UPPER (col1));
ANALYZE TABLE a COMPUTE STATISTICS;
28. Resizing Tablespace without adding datafile
Yet another DDL query to resize table space.
ALTER DATABASE DATAFILE '/work/oradata/STARTST/STAR02D.dbf' resize
2000M;
29. Checking autoextend on/off for Tablespaces
s.status "Status",
p.spid,
sql_text sqltext
FROM v$sqltext_with_newlines t, V$SESSION s, v$process p
WHERE
t.address = s.sql_address
AND p.addr = s.paddr(+)
AND t.hash_value = s.sql_hash_value
ORDER BY s.sid, t.piece;
Performance related queries
36.
Displays CPU usage for each User. Useful to understand database load by
user.
SELECT ss.username, se.SID, VALUE / 100 cpu_usage_seconds
FROM v$session ss, v$sesstat se, v$statname sn
WHERE
se.STATISTIC# = sn.STATISTIC#
AND NAME LIKE '%CPU used by this session%'
AND se.SID = ss.SID
AND ss.status = 'ACTIVE'
AND ss.username IS NOT NULL
ORDER BY VALUE DESC;
37. Long Query progress in database
Show the progress of long running queries.
SELECT a.sid,
a.serial#,
b.username,
opname OPERATION,
target OBJECT,
TRUNC (elapsed_seconds, 5) "ET (s)",
TO_CHAR (start_time, 'HH24:MI:SS') start_time,
ROUND ( (sofar / totalwork) * 100, 2) "COMPLETE (%)"
FROM v$session_longops a, v$session b
WHERE
a.sid = b.sid
AND b.username NOT IN ('SYS', 'SYSTEM')
AND totalwork > 0
ORDER BY elapsed_seconds;
38. Get current session id, process id, client process id?
This is for those who wants to do some voodoo magic using process ids
and session ids.
SELECT b.sid,
b.serial#,
a.spid processid,
b.process clientpid
FROM v$process a, v$session b
WHERE a.addr = b.paddr AND b.audsid = USERENV ('sessionid');
o
SELECT *
FROM ( SELECT ROWNUM,
SUBSTR (a.sql_text, 1, 200) sql_text,
TRUNC (
a.disk_reads / DECODE (a.executions, 0, 1, a.executions))
reads_per_execution,
a.buffer_gets,
a.disk_reads,
a.executions,
a.sorts,
a.address
FROM v$sqlarea a
ORDER BY 3 DESC)
WHERE ROWNUM < 10;
Oracle SQL query over the view that shows actual Oracle
connections.
SELECT osuser,
username,
machine,
program
FROM v$session
ORDER BY osuser;
Oracle SQL query that show the opened connections group by the
program that opens the connection.
The query can come quite handy when you have comma separated data
string that you need to convert into table so that you can use other SQL
queries like IN or NOT IN. Here we are converting AA,BB,CC,DD,EE,FF
string to table containing AA, BB, CC etc. as each row. Once you have this
table you can join it with other table to quickly do some useful stuffs.
WITH csv
AS (SELECT 'AA,BB,CC,DD,EE,FF'
AS csvdata
FROM DUAL)
SELECT REGEXP_SUBSTR (csv.csvdata, '[^,]+', 1, LEVEL) pivot_char
FROM DUAL, csv
CONNECT BY REGEXP_SUBSTR (csv.csvdata,'[^,]+', 1, LEVEL) IS NOT
NULL;
Find the last record from a table
This ones straight forward. Use this when your table does not have
primary key or you cannot be sure if record having max primary key is
the latest one.
SELECT *
FROM employees
WHERE ROWID IN (SELECT MAX (ROWID) FROM employees);
(OR)
sign_val
AS (SELECT CASE MOD (COUNT (*), 2) WHEN 0 THEN 1 ELSE -1 END
val
FROM tbl
WHERE num < 0)
SELECT EXP (SUM (LN (ABS (num)))) * val
FROM tbl, sign_val
GROUP BY val;
Generating Random Data In Oracle
You might want to generate some random data to quickly insert in table
for testing. Below query help you do that. Read this article for more
details.
This one can be written in multiple ways. You can create count(*) on a
table to know number of rows. But this query is more efficient given the
fact that we are only interested in knowing if table has any data.
SELECT 1
FROM TABLE_NAME
WHERE ROWNUM = 1;
If you have some cool query that can make life of other Oracle developers
easy, do share in comment section.
DBCC SHOW_STATISTICS
If youre just getting started as a DBA, accidental or otherwise, these are the
ones you should start memorizing now, because youre going to need them
frequently. My article Using SQL Prompt to Accelerate the Top 10 Most
Common Database Scripts shows how to create a set of DBA snippets from
these scripts, so you can run each of them with one or two simple
keystrokes.
#1 sp_who2 / sys.dm_exec_requests / sp_whoisactive
For several reasons, I lumped these three scripts together. While I was very
explicit in asking people not to nominate third party scripts, Adam
Machanics sp_whoisactive kept showing up over and over again, so I
decided that I couldnt very well keep it off the list.
The sp_whoisactive script uses various DMVs to investigate current activity
on the system. It will highlight, among other things, which queries are
running long and where you might be experiencing blocking. Under the
covers, it makes use of the sys.dm_exec_requests Dynamic Management
View (DMV), so I decided to keep them together. The tool sp_who2 represents
the old way of looking at current activity on the system, and Im including it
here too mainly because I want people to stop using it. Instead,
use sys.dm_exec_requests and the associated DMVs to find this information
(or sp_whoisactive).
There are lots of ways to put together information out of these DMVs. Heres
one example that shows you whats currently running on the system, the
query text and the execution plan.
SELECT *
FROM sys.dm_exec_requests AS der
CROSS APPLY sys.dm_exec_sql_text(der.sql_handle) AS dest
CROSS APPLY sys.dm_exec_query_plan(der.plan_handle) AS deqp;
GO
Listing 1
Armed with a simple script like this, you can quickly and easily see
everything that you can see through sp_who2. Using the same data (the
same FROM clause), you can start to slice and dice it in interesting ways.
Heres an example, which I dont expect you to memorize:
SELECT SUBSTRING(dest.text, ( der.statement_start_offset / 2 ) + 1,
( CASE der.statement_end_offset
WHEN -1 THEN DATALENGTH(dest.text)
ELSE der.statement_end_offset
- der.statement_start_offset
END ) / 2 + 1) AS querystatement ,
deqp.query_plan ,
der.session_id ,
der.start_time ,
der.status ,
DB_NAME(der.database_id) AS DBName ,
USER_NAME(der.user_id) AS UserName ,
der.blocking_session_id ,
der.wait_type ,
der.wait_time ,
der.wait_resource ,
der.last_wait_type ,
der.cpu_time ,
der.total_elapsed_time ,
der.reads ,
der.writes
FROM sys.dm_exec_requests AS der
CROSS APPLY sys.dm_exec_sql_text(der.sql_handle) AS dest
CROSS APPLY sys.dm_exec_query_plan(der.plan_handle) AS deqp;
GO
Listing 2
STATISTICS IO ON;
STATISTICS TIME ON;
STATISTICS IO OFF;
STATISTICS TIME OFF;
Listing 3
Simply replace the ellipsis with your query, in Listing 3, and youll see a set
of messages to written to Messages output within the SSMS query window,
the amount of time spent on the query and the reads and writes the query
causes.
Figure 1
You can see the basics right at the top, describing the table in question, the
table owner and data the table was created. Below that, you start seeing
details. The second section shows the columns, such as the IDENTITY column
and its definition.
Storage, indexes and constraints are all detailed, and finally information
about which foreign keys reference this table.
If youre not sure about a database or its design, sp_help is a quick, easy,
and most importantly programmatic way to identify details about the objects
within it.
#5 DBCC SQLPERF
Most DBAs have been taken by surprise, at one time or another, by
extremely rapid growth in the size of the transaction log. It can be cause by
lack of log backups, or infrequent log backups, or by some other problem,
Figure 2
In addition, you can also use DBCC SQLPERF to reset the statistics gathered
on Waits and Latches by issuing commands to clear them.
DBCC SQLPERF("sys.dm_os_latch_stats" , CLEAR);
DBCC SQLPERF("sys.dm_os_wait_stats" , CLEAR);
GO
Listing 7
Just remember, this resets these statistics completely to zero, so you wont
have any historical track from the moment you run the above commands.
#6 sys.dm_exec_query_stats
If sys.dm_exec_requests is the place to go to find out what requests are
running on the server right now, then sys.dm_exec_query_stats is where
youll find aggregated, server-wide data summarizing previous activity.
It shows aggregations of performance metrics on statements within queries,
procedures and batches. However, this information is only retained on the
queries that are currently stored in cache. As soon as the query leaves the
cache, this information goes away completely. If the query comes back into
cache, it starts over at scratch gathering its metrics. You use this DMV in
similar ways to sys.dm_exec_requests.
SELECT SUBSTRING(dest.text, ( deqs.statement_start_offset / 2 ) + 1,
( CASE deqs.statement_end_offset
WHEN -1 THEN DATALENGTH(dest.text)
ELSE deqs.statement_end_offset
- deqs.statement_start_offset
END ) / 2 + 1) AS querystatement ,
deqp.query_plan ,
deqs.execution_count ,
deqs.total_worker_time ,
deqs.total_logical_reads ,
deqs.total_elapsed_time
FROM sys.dm_exec_query_stats AS deqs
CROSS APPLY sys.dm_exec_sql_text(deqs.sql_handle) AS dest
CROSS APPLY sys.dm_exec_query_plan(deqs.plan_handle) AS deqp;
Listing 8
Queries against sys.dm_exec_query_stats, especially when combined with
other DMVs, can provide meaningful and useful information, but just
remember that these are aggregates, so it wont show individual parameter
values or row counts or other results related to individual executions of the
query.
You can also look to sys.dm_exec_procedure_stats to see the same kind of
information on stored procedures.
#7 RESTORE DATABASE
On the one hand, Im rather shocked to see RESTORE DATABASE so far down
the list. On the other hand, when I think about the number of backups I have
done versus the number of times Ive used those backups to restore a
database, it makes sense. On the gripping hand, Im not surprised that it
made the list because weve all had to restore a backup or three.
Entire articles have been written about all the details of
the RESTORE process. Listing 9 shows one use of RESTORE that comes up a
lot, namely creating a new database from the BACKUP file.
RESTORE DATABASE ADW
FROM DISK = 'D:\bu\adw.bak'
WITH MOVE 'AdventureWorks2014_Data' TO 'E:\data\adwnew.mdb',
MOVE 'AdventureWorks2014_Log' TO 'F:\log\adwnewlog.ldb',
NORECOVERY;
Listing 9
The basics of the command are second nature to most DBAs. You have to
define which database youre restoring and then you have to deal with the
files. In this case, Im moving the data to a new location, with new names, in
order to be able to restore a database to the same server that already has a
copy of this database. Finally, I use the NORECOVERY option so that I can
validate the RESTORE process before I open the database up to people. As a
final step you just run RESTORE...WITH RECOVERY.
RESTORE DATABASE ADW
WITH RECOVERY;
GO
Listing 10
#8 RESTORE FILELISTONLY
Closely related to RESTORE DATABASE is RESTORE FILELISTONLY. If you have
to run a restore, youre going to want to know what the logical names and
physical locations of the files. Further, youre going to want to know how
many filesyou have because databases can have multiple data files, all of
which have to be used during a RESTORE (not counting piece
meal RESTOREs). The syntax is very simple.
RESTORE FILELISTONLY
FROM DISK = 'c:\bu\adw.bak';
Listing 11
The results are very thorough. Im going to just show a small sub-section of
all the details:
LogicalName
AdventureWorks2014_Data
AdventureWorks2014_Log
You can see everything you need to feedback to the RESTORE
DATABASE operation (#7).
#9 sp_spaceused
One of the primary tasks youre going to find yourself doing as a DBA is
managing files on disks and worrying about disk space. One of the ways
youre going to worry about it is by investigating the individual objects,
tables and indexes, which are using up your disk space. Thats
where sp_spaceused comes in handy.
EXEC sys.sp_spaceused @objname = N'Sales.SalesOrderHeader';
Listing 12
The results are easy to understand.
Figure 3
If we dont supply an object name, i.e. just run EXEC sys.sp_spaceused, then
well see results for the entire database, and return a very different set of
results.
Figure 4
One additional argument that is worth noting is @updateusage, which when
set to true will run DBCC UPDATUSAGE. It will rescan the system views that
store this data and update pages and row counts so that they report more
accurate size and space information.
For example, Listing 13 reruns sys.sp_spaceused for
our SalesOrderheader table.
EXEC sys.sp_spaceused @objname = N'Sales.SalesOrderHeader',
@updateusage = 'true';
GO
Listing 13
Ill get a slightly different set of results:
Figure 5
We now see a slightly different set of values form those shown in Figure 3;
note that the reserved, index_size and unused values have changed.
Running DBCC UPDATUSAGE can result in additional I/O load on your system,
so exercise caution.
Many people have stopped using sp_spaceused in favor of directly querying
the system tables and DMVs for object usage information. However, my
survey results indicate the enduring popularity of sp_spaceused.
#10 DBCC SHOW_STATISTICS
Coming in at #10 is DBCC SHOW_STATISTICS. Again, Im surprised it came in
so far down the list. Maybe Ive had to deal with bad parameter sniffing too
many times. Maybe I just do lots of index and query tuning. Whatever the
cause, I look at the statistics on my tables and indexes more than my peers,
but clearly, theyre looking at them too since this command made the list.
If you want to see how SQL Server thinks your data looks to the optimizer,
statistics are the answer. The syntax for retrieving them is pretty clear.
DBCC SHOW_STATISTICS('Sales.SalesOrderHeader',
'PK_SalesOrderHeader_SalesOrderID');
Listing 14
You just provide the table name and the name of the set of statistics in which
youre interested. In this example, Im looking at the primary key. The results
come in three parts.
Figure 6
At the top is the header which provides some general information. Next is
the density graph which shows the uniqueness or selectivity of the column or
columns that make up this set of statistics. Finally, you have the histogram,
up to 200 steps showing the data distribution of the first column out of
however many columns there are in this set of statistics. I chose to show the
primary key for the table so that you can see how, despite there being
31,465 rows in the table, the histogram only shows two steps. This is
because every single one of those rows is unique for the primary key value,
so the distribution doesnt need 200 steps to show how things are laid out
within the data.
Conclusion
Few if any of the scripts that appear on the Ten Most Common Database
Scripts were a real surprise. The interesting thing for me was the variation in
how individuals use these scripts or arrive at their own version of these
scripts. Everyone out there has tasks in common. Everyone out there has
tasks that are unique to them. Everyone out there finds new ways to solve
these tasks, but most of us use a common set of tools.
I hope these scripts are helpful to anyone finding their way into the DBA role.
SQL*Plus User's Guide and Reference
SQL*Plus Quick Start
These instructions are to enable you to login and connect to a database after
you have installed SQL*Plus. You can connect to the default database you
created during installation, or to another existing Oracle database.
SQL*Plus Resources
SQL*Plus Overview
SQL*Plus Prerequisites
Starting SQL*Plus Command-line
Starting SQL*Plus Windows GUI
Starting iSQL*Plus
Starting SQL*Plus Instant Client
Connecting to a Different Database
Sample Schemas and SQL*Plus
Running your first Query
Exiting SQL*Plus
SQL*Plus Resources
SQL*Plus Overview
SQL*Plus is an interactive and batch query tool that is installed with every
Oracle Database installation. It has a command-line user interface, a
Windows Graphical User Interface (GUI) and the iSQL*Plus web-based user
interface.
There is also the SQL*Plus Instant Client which is a stand-alone commandline interface available on platforms that support the OCI Instant Client.
SQL*Plus Instant Client connects to any available Oracle database, but does
not require its own Oracle database installation. See the Oracle Call Interface
Programmer's Guide for more information on the OCI Instant Client.
SQL*Plus has its own commands and environment, and it provides access to
the Oracle Database. It enables you to enter and execute SQL, PL/SQL,
SQL*Plus and operating system commands to perform the following:
Format, perform calculations on, store, and print from query results
Examine table and object definitions
If using iSQL*Plus, ensure that you have the URL for the Application
Server you want to connect to, and that the Application Server is
available and running. See Starting the iSQL*Plus Application Server,
and Testing if the iSQL*Plus Application Server is Running.
sqlplus hr@MYDB3
The TWO_TASK (on UNIX) or LOCAL (on Windows) environment variable can
be set to a connection identifier. This removes the need to explicitly enter
the connection identifier whenever a connection is made in SQL*Plus or
SQL*Plus Instant Client. This UNIX example connects to the database known
as MYDB4:
TNS_ADMIN=/home/user1
export TNS_ADMIN
TWO_TASK=MYDB4
export TWO_TASK
sqlplus hr
To start SQL*Plus and connect to the default database
1. Open a UNIX or a Windows terminal and enter the SQL*Plus command:
2. sqlplus
3. When prompted, enter your Oracle Database username and password.
If you do not know your Oracle Database username and password, ask
your Database Administrator.
4. Alternatively, enter the SQL*Plus command in the form:
5. sqlplus username
You are prompted to enter your password.
6. SQL*Plus starts and connects to the default database.
Now you can start entering and executing SQL, PL/SQL and SQL*Plus
statements and commands at the SQL> prompt.
To start SQL*Plus and connect to a database other than the default
Open a UNIX or a Windows terminal and enter the SQL*Plus command:
sqlplus username@connect_identifier
You are prompted to enter your password.
Starting SQL*Plus Windows GUI
To start the SQL*Plus Windows GUI and connect to a database
1. Click Start > Programs > Oracle-OraHomeName > Application
Development > SQL Plus.
2. Alternatively, open a Windows terminal and enter the SQL*Plus
command:
3. sqlplusw
4. The SQL*Plus Windows GUI opens and the Log On dialog is displayed.
Enter your Oracle Database username and password in the Log On
dialog. If you do not know your Oracle Database username and
password, ask your Database Administrator.
Leave the Host String field blank to connect to the default database.
Enter a connection identifier for the database you want to connect to in
the Host String field. You can connect to Oracle8i, Oracle9i and Oracle
Database 10g databases.
5. Click OK. SQL*Plus starts and connects to the database.
Now you can start entering and executing SQL, PL/SQL and SQL*Plus
statements and commands at the SQL> prompt.
Starting iSQL*Plus
To start an iSQL*Plus session
1. Enter the iSQL*Plus URL in your web browser's Location or Address
field. The iSQL*Plus URL looks like:
2. http://machine_name.domain:port/isqlplus
If you do not know the iSQL*Plus URL, ask your System Administrator,
or try one of the following on the machine running the iSQL*Plus
Application Server.
http://127.0.0.1:5560/isqlplus/
http://localhost:5560/isqlplus/
iSQL*Plus uses HTTP port 5560 by default. If iSQL*Plus is not available
on port 5560, read the $ORACLE_HOME/install/portlist.ini file on the
computer running the iSQL*Plus Application Server to find the port on
which iSQL*Plus is running.
3. Press Enter to go to the URL. The iSQL*Plus Login screen is displayed in
your web browser.
4. Enter your Oracle Database username and password in the Username
and Password fields. If you do not know your Oracle Database
username and password, ask your Database Administrator.
5. Leave the Connection Identifier field blank to connect to the default
database.
Enter an Oracle Database connection identifier in the Connection
Identifier field to connect to a database other than the default. You can
connect to Oracle8i, Oracle9i and Oracle Database 10g databases.
If restricted database access has been configured, the Connection
Identifier field is a dropdown list of available databases to select.
6. Click Login to connect to the database. The iSQL*Plus Workspace is
displayed in your web browser.
Now you can start entering and executing SQL, PL/SQL and SQL*Plus
statements and commands in the Workspace.
Starting and Stopping the iSQL*Plus Application Server
The iSQL*Plus Application Server is started during Oracle Database
installation. It must be running to enable web-based iSQL*Plus sessions.
See Starting the iSQL*Plus Application Server.
Starting SQL*Plus Instant Client
SQL*Plus Instant Client is the SQL*Plus command-line without the need to
install Oracle Database. For information about using it, see Starting SQL*Plus
Command-line.
SQL> @?\DEMO\SCHEMA\HUMAN_RESOURCES\HR_MAIN.SQL
To remove the sample tables, perform the same steps but substitute
HR_DROP.SQL for HR_MAIN.SQL.
Running your first Query
To describe a database object using iSQL*Plus, for example, column details
for EMP_DETAILS_VIEW, enter a DESCRIBE command like:
DESCRIBE EMP_DETAILS_VIEW
which produces the following output:
To rename the column headings, and to select data from the HR sample
schema view, EMP_DETAILS_VIEW, enter
COLUMN FIRST_NAME HEADING "First Name"
COLUMN LAST_NAME HEADING "Family Name"
Exiting SQL*Plus
It is recommended that you always use the Logout icon to exit iSQL*Plus to
free up system and server resources.
To exit SQL*Plus command-line, enter EXIT.
To exit the Windows GUI, enter EXIT or select Exit from the File menu.
In iSQL*Plus, the EXIT or QUIT command halts the script currently running, it
does not terminate your session.
Previous Page
Page 7 of 83
Next Page
About Oracle
Contact Us
Legal Notices
Terms of Use
Your Privacy Rights
Copyright 2016, Oracle and/or its affiliates. All rights reserved.
iostat
iostat
iostat
iostat
iostat
PM
PM
PM
PM
CPU
%user
%nice %system %iowait
%idle
all
16.92
0.00
1.48
0.15
81.45
all
14.65
0.00
0.80
0.10
84.45
all
15.85
0.00
2.02
0.07
82.05
all
15.81
0.00
1.43
0.11
82.65
About Me
Ed
View my complete profile
Disclaimer
This blog was created to document some of the common used command
related to Unix Operating System. If you intend to use the command found in
this blog, please use with care and make sure you understand it's function
before applying it on your system. The owner of this blog and author of any
article found in this blog shall not be liable for any loss or damage of
whatever nature arising from the article found in this blog. If you identify any
such content that is harmful, malicious, sensitive or unnecessary in this blog,
I request you to contact me via email [edtishere@gmail.com] so I may rectify
the problem.
Simple template. Powered by Blogger.
Skip to content
O RAC L E D B A A H E L P I N G H A N D
RA J E E V KU M A R J H A D O M A I N H E A D O RAC L E ( O C P 9 I , 1 0 G , 1 1 G
& O RA C L E C E RT I F I E D E X P E RT , O RAC L E R E A L A P P L I C AT I O N
C LU S T E R S 1 1 G A N D G R I D I N F RA S T R U C T U R E A D M I N I S T RAT O R )
HOME
ORACLE DBA (A HELPING HAND)
PERFORMANCE TUNING
ORACLE REPLICATION
DATABASE ADMINISTRATION
DATABASE MAINTENANCE TASKS
BACKUP & RECOVERY
DATA GUARD
DATABASE ARCHITECTURE
ORACLE RAC
SCRIPTS
ORACLE 12C
INTERVIEW QUESTIONS
ABOUT
S T E P BY S T E P D ATA B A S E R E F R E S H.
December 25, 2015
In this post I am going to describe you step by step process for database
refresh using datapump (EXPDP/IMPDB). In this example my source database
name is MYDB where target database is AVANI
I found many DBA forget to restore old password while import or not
checking invalid object before giving ok to requester who requested for
database refresh from production to test or development databases.
Please find the step by step process which you can follow in your
environments.
1. Always remember to Check the database name before export or import.
SQL> select name from v$database;
NAME
MYDB
2. Check the space utilise of by schema before export.
SQL> select owner,sum(bytes)/1024/1024 MB from dba_segments group
by owner;
OWNER
MB
SYSTEM
30
SYS
715.0625
WMSYS
1.1875
RAJEEV
111
WKSYS
1.625
OUTLN
.5625
DBSNMP
.75
3. Check the username and tablespace before export so you can compare
thing before import.
SQL> col ACCOUNT_STATUS for a10
SQL> col profile for a15
SQL> set lines 150
SQL> select
USERNAME,ACCOUNT_STATUS,DEFAULT_TABLESPACE,TEMPORARY_TABLESPA
CE,PROFILE from dba_users where username=RAJEEV;
USERNAME ACCOUNT_ST DEFAULT_TABLESPACE TEMPORARY_TABLESPACE
PROFILE
RAJEEV OPEN DATA01 TEMP DEFAULT
4. Note the password of schema for export and do same on target database
before import, it can help you when you need to maintain old password.
SQL> set long 2000
SQL> select dbms_metadata.get_ddl(USER,RAJEEV) from dual;
DBMS_METADATA.GET_DDL(USER,RAJEEV)
CREATE USER RAJEEV IDENTIFIED BY VALUES
S:3AFD2F1934CCFB63E4793D84FC8
F1D663550D0D07EEADEE4005F8C46807F;5BE571F865FDADE0
DEFAULT TABLESPACE DATA01
TEMPORARY TABLESPACE TEMP
5. Check the tablespaces used be schema before export
DATA01
6. Check all objects and there status before export. It can help you compare
your object after import.
SQL> select object_type, count(1) from dba_objects where owner=RAJEEV
group by rollup(object_type);
OBJECT_TYPE
FUNCTION
INDEX
PACKAGE
PACKAGE BODY
PROCEDURE
SEQUENCE
TABLE
TRIGGER
TYPE
VIEW
COUNT(1)
32
134
2
2
494
1
93
57
45
9
869
11 rows selected.
SQL> select object_type,status,count(1) from dba_objects where
owner=RAJEEV group by object_type,status;
OBJECT_TYPE
STATUS COUNT(1)
- - TYPE
VALID
45
PROCEDURE
VALID
494
FUNCTION
VALID
32
PACKAGE BODY
VALID
2
PACKAGE
VALID
2
VIEW
VALID
9
INDEX
VALID
134
SEQUENCE
VALID
1
TRIGGER
TABLE
VALID
VALID
57
93
7. Check objects status if any invalid before export. In this example no invalid
object on source.
SQL> select distinct status from dba_objects where owner=RAJEEV;
STATUS
VALID
8. Check the database dictionary before export. So you have idea where you
have to export and which location your export file will be kept.
SQL>
SQL> SELECT owner, directory_name, directory_path
FROM all_directories;
9. I prefer to create par file for export and import it can be done without par
file also.
Create par file with the help of vi editor or any text file. Here i am using
simple par file for demo purpose we can use complex query as well in par
file.
vi expdp_RAJEEV.par
DIRECTORY=DP_MYDB
SCHEMAS=RAJEEV
DUMPFILE=MYDB_RAJEEV_04DEC2013.DMP
LOGFILE=EXPDP_MYDB_RAJEEV_04DEC2013.log
10. Now i am going to call par file for this export. It can be done from
command prompt also.
nohup expdp \/ as sysdba\ parfile=expdp_RAJEEV.par &
Or
nohup expdp system/password DIRECTORY=DP_MYDB
DUMPFILE=MYDB_RAJEEV_04DEC2013.DMP SCHEMAS=RAJEEV
LOGFILE=EXPDP_MYDB_RAJEEV_04DEC2013.log &
11. Now copy the export file on target server for import. Go to the location
wher your export file is available and copy it. Make sure you have privilage of
copy the dump on target server on mentioned lcoation.
scp EXPDP_MYDB_RAJEEV_04DEC2013.log
rajeev@targetserver:/orasav/AVANI/bkp/exp .
**************************************************************targetserver***
******************************************************************************
*******
12. Check the database name before import. Dont forget to check database
name, we found sevral dba done mistake and import will happen in deafult
database which is pre selected.
SQL> select name from v$database;
NAME
AVANI
13. Check the schme avilable on target database or not if yes space
utilisation need to check before import.
SQL> select owner,sum(bytes)/1024/1024 from dba_segments group by
owner;
OWNER
SYSTEM
SYS
RAJEEV
OUTLN
DBSNMP
SUM(BYTES)/1024/1024
29.875
683.3125
106.25
.5625
,6875
14. Check the tablespaces used be schema before import. If required you can
create tablespace or use remap_schema
SQL> col ACCOUNT_STATUS for a10
SQL> col profile for a15
SQL> set lines 150
SQL> select
USERNAME,ACCOUNT_STATUS,DEFAULT_TABLESPACE,TEMPORARY_TABLESPA
CE,PROFILE from dba_users where username=RAJEEV;
DIRECTORY=DP_AVANI
SCHEMAS=RAJEEV
DUMPFILE=EXPORT_RAJEEV_MYDBP_12-17-14.dmp
LOGFILE=IMPDP_MYDB_RAJEEV_12-17-14.log
19. Now i am going to call par file for import. It can be done from command
prompt also as we have done during export.
nohup impdp \/ as sysdba\ parfile=impdp_RAJEEV.par &
20 Check all objects and there status after import. If any invalid object please
recompile it.
SQL> select object_type,status,count(1) from dba_objects where owner=HR
group by object_type,status;
OBJECT_TYPE
STATUS COUNT(1)
- - FUNCTION
VALID
75
PACKAGE BODY
VALID
1
PROCEDURE
VALID
2
PACKAGE
VALID
1
VIEW
VALID
35
INDEX
VALID
586
SEQUENCE
VALID
120
FUNCTION
INVALID
1
TRIGGER
VALID
121
VIEW
INVALID
1
TABLE
VALID
211
OBJECT_TYPE
STATUS COUNT(1)
- - TRIGGER
INVALID 6
12 rows selected.
21. Check objects status if any invalid after import. In this example i have
invalid object and we need to recompile it if required as we know my source
dont have any invalide object.
SQL> select distinct status from dba_objects where owner=RAJEEV;
STATUS
-
VALID
INVALID
ALTER TRIGGER AUDUPD_TM_PROFILE COMPILE;
******************************* END of database refresh
******************************
If any other object is invalid you can try to compile like below mentioned
steps.
SELECT owner,
object_type,
object_name,
status
FROM dba_objects
WHERE status = INVALID
and owner=RAJEEV;
SQL> SELECT owner, object_type, object_name, status
FROM dba_objects
WHERE status = INVALID and owner=RAJEEV;
OWNER OBJECT_TYPE OBJECT_NAME STATUS
- - RAJEEV PROCEDURE USP_REPORT_DONNEES_CAP_PROVCRE INVALID
RAJEEV PROCEDURE USP_REPORT_DONNEES_CAP_PROVTIT INVALID
RAJEEV PROCEDURE USP_TRACE_EXPORT_CAP_MODULE INVALID
RAJEEV PROCEDURE USP_REPORT_PROVCREANCEHG INVALID
RAJEEV PROCEDURE USP_REPORT_PROVCREANCERECAP INVALID
RAJEEV PROCEDURE USP_SELECT_ALL_DONNEES_CAP INVALID
6 rows selected.
SQL> select alter ||object_type|| ||object_name|| compile; from
user_objects where object_type=VIEW and status=INVALID;
ALTER FUNCTION GETMACHINE COMPILE;
ALTER TRIGGER AUDINS_TM COMPILE;
ALTER VIEW VDK_SYNC_TRG COMPILE;
EXEC DBMS_DDL.alter_compile(PACKAGE, MY_SCHEMA, MY_PACKAGE);
EXEC DBMS_DDL.alter_compile(PACKAGE BODY, MY_SCHEMA,
MY_PACKAGE);
Search for:
T O P P O S T S & PA G E S
Register
Log in
Entries RSS
Comments RSS
WordPress.com
RECENT POSTS
Oracle Education
TOP 5 Major Reasons Not to Use Oracle Db Links
ORAchk release 12.1.0.2.6 is now available for use.
Recovery Catalog Benefits, features,Costs of Using the
Recovery Catalog
Get password changed time for an oracle user
RECENT COMMENTS
surya on ASM Interview
Questions
dagnachew on UNNAMED File
Error in standby
balaji14 on ASM Interview
Questions
How To Backup Asm
Me on ASM Interview
Questions
Amit on UNNAMED File Error in
standby
ABOUT THE ADMIN
I'm Rajeev Jha (OCP 9i,10g,11g & Oracle Certified 11g RAC Eepert.) Working
as Domain Head Oracle in Banking & Finance sector. I have 10 year
experience in database with Oracle & Microsoft. I also conduct training on
behalf of Oracle University.
BLOG AT WORDPRESS.COM.
Sign in
SQL Protocols
Topics from the Microsoft SQL Server Protocols team Netlibs, TDS, SQL
Browser, etc
Steps to troubleshoot SQL connectivity issues
0
0
We have been seeing and trying to resolve SQL connectivity issue all the
time. I guess it would be helpful if we can put some guidance on how to
resolve connectivity issues. Here comes a proposal based on my experience.
Basically, when you failed to connect to your SQL Server, the issue could be:
1) Network issue,
2) SQL Server configuration issue.
3) Firewall issue,
4) Client driver issue,
5) Application configuration issue.
6) Authentication and logon issue.
Usually, customers see connectivity issue in their applications, but it would
be great if you can follow the steps below to eliminate issues one by one and
post a question on SQL Server Data Access forum if needed.
You might be able to make local connection without a working network, but
thats a special case. For remote connection, a stable network is required.
The first thing to trouble shoot SQL connectivity issues is to make sure the
network we rely on is workable and stable. Please run the following
commands:
ping -a <your_target_machine> (use -4 and -6 for IPv4 and IPv6
specifically)
ping -a <Your_remote_IPAddress>
nslookup (type your local and remote machine name and IP address
multiple times)
Be careful to see any mismatch on the returned results. If you are not able to
ping your target machine, it has high chance that either the network is
broken or the target machine is not running. Its possible the target machine
is behind a firewall and the firewall blocks the packets sent by ping, though.
Windows firewall does not block ping (ECHO) packet by default. The
correctness of DNS configuration on the network is vital to SQL connection.
Wrong DNS entry could cause of all sorts of connectivity issue later. See this
link for example, Cannot Generate SSPI Context error message, Poisoned
DNS.
Step 2: SQL Server configuration issue
You need to make sure the target SQL Server is running and is listening on
appropriate protocols. You can use SQL Server Configuration Manager (SCM)
to enable protocols on the server machine. SQL Server supports Shared
Memory, Named Pipes, and TCP protocols (and VIA which needs special
hardware and is rarely used). For remote connection, NP and/or TCP protocols
must be enabled. Once you enabled protocols in SCM, please make sure
restart the SQL Server.
You can open errorlog file to see if the server is successfully listening on any
of the protocol. The location of errorlog file is usually under:
%ProgramFile%Microsoft SQL Server/MSSQLxx.xxx/MSSQL/Log
If the target SQL instance is a named instance, you also need to make sure
SQL Browser is running on the target machine. If you are not able to access
the remote SQL Server, please ask your admin to make sure all these
happen.
Step 3: Firewall issue
A firewall on the SQL Server machine (or anywhere between client and
server) could block SQL connection request. An easy way to isolate if this is a
firewall issue is to turn off firewall for a short time if you can. Long term
solution is to put exception for SQL Server and SQL Browser.
For NP protocol, please make sure file sharing is in firewall exception list.
Both file sharing and NP use SMB protocol underneath.
For TCP protocol, you need put the TCP port on which the SQL Server listens
on into exception.
For SQL Browser, please put UDP port 1434 into exception.
Meanwhile, you can put sqlservr.exe and sqlbrowser.exe into exception as
well, but this is not recommended. IPSec between machines that we are not
trusted could also block some packets. Note that firewall should never be an
issue for local connections.
Provider: Could not open a connection to SQL Server), please try the
following steps:
a)
Open a file share on your server machine.
b)
Run net view \your_target_machine and net
use \your_target_machineyour_share (You can try Map Network Drive
from Windows Explorer as well)
If you get failure in b), its very likely you have OS/Network configuration
issue, which is not SQL Server specific. Please search on internet to resolve
this issue first.
You can try connection using both Windows Authentication and SQL
Authentication. If the tests with all tools failed, there is a good chance that
steps 1-3 were not set correctly, unless the failure is logon-related then you
can look at step 6.
If you succeeds with some of the tools, but fails with other tools, its probably
a driver issue. You can post a question on our forum and give us the details.
You can also use windowssystem32odbcad32.exe (which ships with
Windows) to test connection by adding new DSN for various drivers, but
thats for ODBC only.
a) If you use SQL auth, mixed authentication must be enabled. Check this
page for reference http://msdn.microsoft.com/en-us/library/ms188670.aspx
b) Make sure your login account has access permission on the database you
used during login (Initial Catalog in OLEDB).
c) Check the eventlog on your system see if there is more information
At last, please post question on our forum. More people could help you over
there. When you post question, you can refer to this link and indicate you
see failure at which step. The most important things for us to troubleshoot
are a) exact error message and b) connection string.
Comments (59)
Name *
Email *
Website
Post Comment
1.
Waleed
June 2, 2008 at 8:13 am
2.
3.
Marker
June 13, 2008 at 7:30 am
I am not able to connect to SQL 2005 DB in windows authentication
mode remotly from web application. Is it required to configure
kerberos auhentication?
What could be the cause of this?
Reply
4.
Victor
June 27, 2008 at 10:59 am
5.
alexwcy@hotmail.com
July 1, 2008 at 4:04 am
Hi, I am having below error in my production server that running
ASP.NET2.0 and SQL Server 2005. Can someone tell me why this
error happen? Thanks.
Source = .Net SqlClient Data Provider
Error = A connection was successfully established with the server,
but then an error occurred during the pre-login handshake.
(provider: SSL Provider, error: 0 Not enough storage is available to
complete this operation.) | at
System.Data.ProviderBase.DbConnectionPool.GetConnection(DbCo
nnection owningObject)
at
System.Data.ProviderBase.DbConnectionFactory.GetConnection(Db
Connection owningConnection)
at
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(D
6.
Ernst
July 17, 2008 at 6:06 pm
Thank for Help on Step 2, it seems SQL Express defaults these all to
off. SO remote access doesnt work.
Reply
7.
Cor
July 22, 2008 at 1:43 pm
I am having occasional/rare connection problems with ADO/ADO
.Net connection pooling. The connections use aliases set up for
TCP/IP. Could the problems be occurring because of Kerberos Ticket
Expiration with the pooled connections or could it be that SQL
Server is Orphaning the pooled connections or could it be some sort
of socket problem? Perhaps someone has another suggestion as to
what may be wrong. I am considering using Named Pipes instead to
get around Kerberos authentication.
Reply
8.
Harvey
July 23, 2008 at 10:50 am
9.
10.
Sarah
11.
PuckStopper
12.
Shai
13.
Nathan
14.
dmickel
15.
SandorVigh
What to do ?
Reply
16.
17.
18.
SM
19.
Sanjay
20.
thussain
21.
akhilpatel2
22.
Thanks.
Xinwei
Reply
23.
Larry Kagan
= 690858
Passive Opens
= 140956
= 650737
= 6829
Current Connections
= 24
Segments Received
= 2971348717
Segments Sent
Segments Retransmitted
= 1947969915
= 5448550
Thank you,
-Larry
Reply
24.
keik
25.
S. Balakrishnan
Reply
26.
S. Balakrishnan
27.
Aaron Barr
28.
Ashu
29.
30.
David Olix
31.
Ana
32.
dpblogs
33.
dpblogs
Jimmy Wu
Reply
34.
Ana
35.
dpblogs
Reply
36.
Karthick
37.
nadia
38.
nadia
I traced it, but I didnt find the character (I didnt write the
character -). I ran my app on different computers, theres no
problem with my app. I reformatted my computer and reinstalled all
the programs, it didnt work. It still had that error
Can someone tell me whats wrong with my application (or
computer)??
Note: Im using VB6 for the interface and SQLServer 2000 for the
database and crystal report for report view. the error occurs when
view reports using crystalr report.
Reply
39.
Moorthy
40.
41.
Saurabh Suri
Nice One.
Reply
42.
cr.net
43.
Jijin
44.
Vijai
45.
Nagaraju Kandagatla
46.
bharati
47.
TonyBromo
48.
kazma
49.
Larry
Reply
50.
Sam
51.
Chris
Reply
52.
Arturo Equihua
53.
mohamed
ADDITIONAL INFORMATION:
A network-related or instance-specific error occurred while
establishing a connection to SQL Server. The server was not found
or was not accessible. Verify that the instance name is correct and
that SQL Server is configured to allow remote connections.
(provider: TCP Provider, error: 0 No connection could be made
because the target machine actively refused it.) (Microsoft SQL
Server, Error: 10061)
For help, click: go.microsoft.com/fwlink
B
Reply
54.
Shabbir Bytelink
55.
Koti
56.
Koti
57.
Simon
Reply
58.
Dave
SQL Server was not accessible from the requesting machine. how
we make the 2 machine communicate
Reply
59.
Avi
LOGIN
SearchOracle
SE C TI ON Get Started
by SearchOracle.com experts
Solve your Oracle errors quickly and easily with
help from this fast guide. It covers every expert
response pertaining to Oracle errors on
SearchOracle.com.
Sections
ORA-00000 - ORA-01999
ORA-02000 - ORA-03999
ORA-04000 - ORA-05999
ORA-06000 - ORA-07999
ORA-08000 - ORA-11999
ORA-12000 - ORA-13999
ORA-14000 - ORA-23999
ORA-24000 - ORA-25999
ORA-26000 - ORA-27999
ORA-28000 - ORA-30100
Next Steps
Dig Deeper
Related Content
Sponsored News
A Quick Guide for DBAs: Oracle, the Cloud and All-Flash Storage
Pure Storage
See More
Vendor Resources
Continue Reading
with is not listed, just ask one of our experts for help and we'll add the
response to this ever-growing guide to common Oracle error codes.
ORA-00000 - ORA-01999
ORA-00054: resource busy and acquire with NOWAIT specified
Solutions:
ORA-00313: open failed for members of log group string of thread string
Solutions:
ORA-00381: cannot use both new and old parameters for buffer cache size
specification
Solutions:
Substitution variables
Information on ORA-00980
When rebooting 9i
Input/output errors
Input/output errors
ORA-01157: cannot identify/lock data file string - see DBWR trace file
Solutions:
ORA-01555: snapshot too old: rollback segment number string with name
"string" too small
Solutions:
ORA-01593: rollback segment optimal size (string blks) is smaller than the
computed initial size (string blks)
Solutions:
Solving ORA-03001
ORA-03232 error
ORA-04000 - ORA-05999
ORA-04030: out of process memory
Solutions:
Resolving ORA-04091
ORA-06000 - ORA-07999
ORA-06401: NETCMN: invalid driver designator
Solutions:
What is ORA-06512?
ORA-08000 - ORA-11999
ORA-10033: sort run information (SRD*/SRS*)
Solutions:
ORA-12000 - ORA-13999
ORA-12154: TNS-12154: TNS:could not resolve service name
Solutions:
On home computer
Causes
Uninstalling Oracle9i
ORA-14000 - ORA-23999
ORA-1650: unable to extend rollback segment R05 by 512 in tablespace
RBS Failure to extend rollback segment 6 because of 1650 condition.
Solutions:
ORA-24000 - ORA-25999
ORA-24008: queue table string.string must be dropped first
Solutions:
ORA-26000 - ORA-27999
ORA-27038: skgfrcre: file exists
Solutions:
Input/output errors
Input/output errors
ORA-28000 - ORA-30100
ORA-28030: Server encountered problems accessing LDAP directory service
Solutions:
Hit an error
Next Steps
Avoid errors when copying Oracle Database 9i to a new server
Find out why this error kept TNS listener from connecting
Learn to use Oracle Data Recovery Advisory for database backup and
recovery
Get more information on Oracle Business Accelerators and how they can
speed up ERP deployment
Learn three tips for using Oracle insert syntax
Load
ALL
NEWS
E VALU ATE
M AN AGE
Oldest
[-]
DATA MANAGEMENT
BUSINESS ANALYTICS
SAP
SQL SERVER
JAVA
DATA CENTER
CONTENT MANAGEMENT
FINANCIAL APPLICATIONS
SearchDataManagement
Embedded analytics to feel widest impact of machine learning projects
Amazon Web Services history set the stage for cloud data grab
Seeing the future is hard, as a look into Amazon Web Services history
can show. Now, though, it's clear that the cloud leader ...
About Us
Contact Us
Privacy Policy
Advertisers
Business Partners
Media Kit
Corporate Site
Contributors
Reprints
Archive
Site Map
Answers
E-Products
Events
Features
Guides
Opinions
Photo Stories
Quizzes
Tips
Tutorials
Videos