Hot answers tagged linux
17
You need to recreate the control file
This post by Kaunain Ahmed describes the necessary steps:
do: alter database backup controlfile to trace;
extract the "create controlfile" command from the
background-dump-destination tracefile.
shutdown the DB.
Change the DB-Name in your init.ora and change the init.ora
Change the SID in the ...
10
Since 9i dbnewid utility (nid) can be used to change database name
(and DBID if required).
If database name being changed only then resetlogs is not required:
1. startup database in mount mode
shutdown immediate
startup mount
2. run nid to change database name:
nid target=sys/syspassword@dbtns dbname=newname setname=YES
3. shutdown and ...
10
The real answer will be in the PostgreSQL logs, in /var/lib/pgsql/data/pg_log.
However, before you take any action: It is vital that you take a file system level copy of your database before attempting repair if any of your data is valuable to you. See http://wiki.postgresql.org/wiki/Corruption . You must copy the whole data directory. On Fedora that's ...
8
All Data is InnoDB
This is what will give you an exact point-in-time snapshot of the data:
mysqldump -uuser -ppass --single-transaction --routines --triggers --all-databases > backup_db.sql
--single-transaction produces a checkpoint that allows the dump to capture all data prior to the checkpoint while receiving incoming changes. Those incoming ...
6
Yes, you can and it is quite easy too.
In Oracle, the ORACLE_SID is just the name for the Oracle Instance and has not very much to do with the DBNAME. A database with the name PROD, can be served using Instances with any valid name. There is no direct connection between the SID and the DBNAME. This connection is made using the parameters.
The parameter ...
6
I don't think it's a matter of performance but of management.
With separate file per table, you can store different databases in different storage devices for example.
You can deal with the case of very large databases in file systems that can't handle big files (at least postpone the problem until one table reaches the file size limit).
You don't have ...
6
1a. Warm standby is a "live", incremental backup fed with complete blocks of changes (wal segments) 16 mb each, that are send to the standby node once they're filled. You cannot query a warm standby node. 16 mb of changes (by default) can mean a lot of transactions, should the master fail, they'll be lost.
1b. Hot Standby. (also a "live" incremental backup) ...
5
I would be very surprised if there was a generic tool for this - how would it "know" what is sensitive data and what wasn't? For example it would need to examine all your data and recognize all possible formats of credit card number, phone number, postcode, email address, and whatever other data is considered sensitive. It would also need to be smart about ...
5
Migrating between two very different DBMS requires a lot more than just migrating the data. But migration of the data is usually the easiest part.
The way that I have tried, which is free and I can confirm that it works:
create a mysql schema only dump
Adjust the SQL using a text editor and a lot of search and replace
run the converted SQL in Postgres
...
5
According to the MySQL Documentation, the InnoDB Buffer Pool is set to 128MB by default in MySQL 5.5.
You can show how much of the InnoDB Buffer Pool is in use and reserved as follows:
SELECT
BufferPoolUsed BytesUsed,
(BufferPoolUsed / power(1024,1)) UsedKB,
(BufferPoolUsed / power(1024,2)) UsedMB,
(BufferPoolUsed / power(1024,3)) UsedGB,
...
5
Memory usage in linux in general and for Postgres in particular is a pretty complex subject, a good starting point is Bruce Momjians blog covering the subject and the usage of smem. It is well worth following the links in Chris Seibenmanns blog on the subject.
5
Your database is unhappy.
Login to your Linux box as the DB owner user (usually oracle), restart it & then do the following to recreate the broken data dictionary objects:
sqlplus / as sysdba
@?/rdbms/admin/catrepr.sql
@?/rdbms/admin/catrep.sql
@?/rdbms/admin/utlrp.sql
Restart the database once done.
This is an unusual situation to be in - Has ...
5
There is no reason why Oracle would perform badly on Ubuntu (though Oracles OEL kernel has some Oracle-specific optimisations), it's all about enterprise support.
Certification is an expensive and time-consuming task, as is training support workers in each flavour of Linux - that's why the RDBMS is only officially supported on a select number of releases.
4
Memory can help you by caching and thus reducing I/O.
However, that won't reduce CPU usage which is your problem. This is an unusual bottleneck, as CPUs are insanely fast for most database work and I/O tends to be the bottleneck.
In your case, it is even more inusual, because you have 16-cores and VPSs tend not to have great I/O performance. First of all, ...
4
I have administered both MySQL and DB2 database systems. In general, I'd say that DB2 requires more memory and more administration. But sometimes, you can use DB2's sophisticated features to perform queries which are much more efficient.
About memory and administration: DB2 is not very good at making good use of RAM. Either you spend a lot of time ...
4
Oracle has an alert log which should tell you when and why it shut down. Depending on how the database was configured, that will be under a directory identified by either the diagnostic_dest or background_dump_dest parameters, and will be called alert.xml or alert.log (in previous versions). If you're running it, you can get information from Enterprise ...
4
This is my reason for never NOT using innodb_file_per_table:
Without file per table, the ibdata file never compresses or shrinks or lessens in space ever. Not when you delete a row, drop a table, or a database. 2GB of data can become a 20GB file in no time if you have an active queuing system.
Let's say you want to make a backup of your current 1GB table ...
4
If you only need to run SQLPlus, grab "Instant Client Package - Basic" and "Instant Client Package - SQL Plus: Additional libraries and executable for running SQL Plus with Instant Client" from http://www.oracle.com/technetwork/topics/linuxsoft-082809.html & install them.
oci.dll is a windows file, so I have no idea what could be achieved by installing ...
4
Your risk is data loss, not data corruption. An ACID platform guarantees transactions are
atomic,
consistent,
isolated, and
durable.
With asynchronous commits, you give up "durable". For your application, that seems a defensible decision.
If you have some transactions that need to be durable (new user registrations?) you can have that, too. PREPARE ...
3
The buffer pool is used by MySQL for caching InnoDB data and indexes in memory.
It is not the total memory used but your MySQL DB
If your InnoDB tables are that small 128MB is more than enough and effectively all InnoDB tables will be treated as in-memory tables. The 128Mb is a limit of how large the buffer can be and it is only filled when needed.
You can ...
3
I had a similar problem. Virtual disks kill performance. Try to get as much data into memory as possible. I eventually put the disk intensive VM's onto its own RAID stack.
Most people in OIT do not recommend putting disk intensive applications into a VM because of this reason. You also didn't specify which VMWare product you are using. ESXi was released for ...
3
For JDBC based tools such as Squirrel you should try to use (even with Oracle8i) a 9.x or even a 10.x driver (not sure about the 10.x though). Maybe they give better performance. Somewhere on the JDBC download page of Oracle there is a compatibility Matrix that shows which driver version is compatible with which database version.
Another cross-platform ...
3
You might want to look at SQL Workbench/J
It's Java/JDBC based thus runs fine on Linux
It supports a GUI mode, interactive commandline usage (no GUI) and can be run in batch mode. It also supports exporting into various formats in order to take the "dump".
3
max_fsm_pages was eliminated in version 8.4. Free space tracking has gotten a lot smarter and more automatic.
Performance of deletes is going to depend on a lot of things.
If there are any foreign keys which reference this table, you should check whether there is an index on the referencing column(s). Without that, each DELETE will cause a scan of the ...
3
MySql uses SHA1 to hash the password in the following way and then prefix's it with a star:
SHA1(SHA1(password));
The argument to the outer SHA1 must be the binary result of the inner hash for it to work properly.
source: MySQL source code and the following link:
http://palominodb.com/blog/2011/12/04/hashing-algorithm-mysql-password
3
In order to find a specific session running a certain script, it is easiest if the scripts makes itself identifiable by using dbms_application_info and dbms_session. See Morgans Library for details. Also see track the parts of my application that are in use for sample code.
Doing so enables you to select on v$session and filter not only on username and ...
3
While not a Graph or RDBMS based solution, let me suggest a NoSQL database. IMO all of your criteria seem like they could be met with a Cassandra/Solr implementation.
We use Cassandra at work for storing large amounts of data, and we serve it to various applications with a JBoss service layer. Cassandra integrates right in with the Apache Solr search ...
3
I have installed 11.2 on Ubuntu (in VMWARE) using this set of instructions:
http://edin.no-ip.com/blog/hswong3i/oracle-database-11g-release-2-ubuntu-12-04-howto
I had to google a few other things, but in general this is by far the best set of instructions I have found. I recommend saving the website and keeping it in a safe place :)
3
The description for the message you're seeing is:
Cause: Most of the listener administrative commands are only intended
to be issued by privileged users, for example DBAs or system
administrators. If the listener password is not set, then the listener
only accepts administrative requests from LSNRCTL running with the
same OS credentials, or ...
3
It will probably cause differences on the slave in the long run. I've had the same warnings (but with INSERT DELAYED, so your mileage may vary), and on a couple of write intensive tables the data would be different a couple of times a week (leading to a lenghty dump and import).
The ordering of some things is not necessarily the same on every mysql server, ...
Only top voted, non community-wiki answers of a minimum length are eligible
