Sponsored Content
Full Discussion: DSEE LDAP corruption
Homework and Emergencies Emergency UNIX and Linux Support DSEE LDAP corruption Post 302416789 by jlliagre on Tuesday 27th of April 2010 05:52:33 PM
Old 04-27-2010
Start by looking at the DSEE error and access log entries before and during the incident to try figuring out what caused the issue.
Also, telling the input data is valid doesn't help. If it triggers an object class violation, either there is something wrong with it or the schema has been modified earlier on the directory server.
"dsadm export" error messages would help too.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

file corruption

Hi, All of a sudden I landed in a strange problem. I was working with my C source code in vi editor. I did a wq! and when reopened, the file is full of "data".. I mean the text contents are gone!!. I believe this is a file corruption. I have tried the -r option with vi, but no success. ... (5 Replies)
Discussion started by: shibz
5 Replies

2. Windows & DOS: Issues & Discussions

NTFS corruption under w2k but not under suse 9.2

Hello all, I´ve bumped into some strange things with a NTFS partition of mine. I am running a dual boot machine with w2k and suse 9.2. I just reinstalled w2k on it. After that one of my NTFS partitions stopped working under windows. Though it is perfectly readable from linux. Windows sees the... (4 Replies)
Discussion started by: mickepe
4 Replies

3. Shell Programming and Scripting

ftp zip files corruption

Hi I have a zip file that I am ftping to another server. After I have ztped the file it is corrupt and cannot be opened by winzip. Can anyone throw any light on to why this would happen. I have no problems with sending the individual files, but when zipped into one file it becomes... (3 Replies)
Discussion started by: colesga
3 Replies

4. UNIX for Advanced & Expert Users

rsync data corruption

Dear Peoples I am using the following command to transfer the files inbetween two servers, i am using this command in a crontab for doing it in every 1 hour on all days. rsync --stats --archive --verbose --compress --force --rsh=ssh --exclude-from=/root/cfg/mkt_scn.exclude... (1 Reply)
Discussion started by: thameema
1 Replies

5. Solaris

Data corruption

I have a solaris 5.6 on which oracle is installed. we have an alert file alert_net1.log now whenever any datacorruption happens we get the file id and block id in the above file. through this file and block id , we try to find out which table is corrupted and then try to... (1 Reply)
Discussion started by: asalman.qazi
1 Replies

6. Solaris

DSEE 6.3.1 with TLS:simple

Hello guys, I have been trying to set up my DSEE 6.3 on Solaris 10 using proxy with tls:simple authentication. I follow all the steps mentioned in the Installation Guide on Sun's site but there is a problem with ldapclient init when I use hostname instead of IP address in the Default Server... (12 Replies)
Discussion started by: niyazi
12 Replies

7. Shell Programming and Scripting

Script for verification of Data corruption

Hi, I am from File system back ground and doing File system testing on Linux, I need script that scirpt that create the different multiple types of .txt, device file and then copy to mount point /mnt/ dir and then verify the created files and copied files, if created files and copied files are... (4 Replies)
Discussion started by: manish_tcs_hp
4 Replies

8. UNIX for Advanced & Expert Users

something like LDAP Administrator 2011.1 "LDAP-SQL" but for the CLI

Hi I am searching a tool like "LDAP Administrator 2011.1"/ "LDAP-SQL" but for the CLI. Wish to use LDAP-SQL in scripts (non Windows GUI environment) http://ldapadministrator.com/resources/english/2011.1/images/sqlquery_large.png Softerra LDAP Administrator 2011.1 - What's New OS is... (2 Replies)
Discussion started by: slashdotweenie
2 Replies

9. UNIX for Advanced & Expert Users

File System corruption

Hi, While a tar file was created, the file system got full and there was no message on the tar failure. Then the system was shut down and the administrator says because the file system was full the shut down procedure corrupted the file system. I'm wondering, unix should have given some... (2 Replies)
Discussion started by: manivanm
2 Replies

10. Solaris

LDAP Client not connecting to LDAP server

I have very limited knowledge on LDAP configuration and have been trying fix one issue, but unsuccessful. The server, I am working on, is Solaris-10 zone. sudoers is configured on LDAP (its not on local server). I have access to login directly on server with root, but somehow sudo is not working... (9 Replies)
Discussion started by: solaris_1977
9 Replies
ovsdb-tool(1)							Open vSwitch Manual						     ovsdb-tool(1)

NAME
ovsdb-tool - Open vSwitch database management utility SYNOPSIS
ovsdb-tool [options] create db schema ovsdb-tool [options] compact db [target] ovsdb-tool [options] convert db schema [target] ovsdb-tool [options] needs-conversion db schema ovsdb-tool [options] db-version db ovsdb-tool [options] schema-version schema ovsdb-tool [options] db-cksum db ovsdb-tool [options] schema-cksum schema ovsdb-tool [options] query db transaction ovsdb-tool [options] transact db transaction ovsdb-tool [options] [-m | --more]... show-log db ovsdb-tool help Logging options: [-v[module[:facility[:level]]]]... [--verbose[=module[:facility[:level]]]]... [--log-file[=file]] Common options: [-h | --help] [-V | --version] DESCRIPTION
The ovsdb-tool program is a command-line tool for managing Open vSwitch database (OVSDB) files. It does not interact directly with running Open vSwitch database servers (instead, use ovsdb-client). Basic Commands create db schema Reads an OVSDB schema from the file named schema and creates a new OVSDB database file named db using that schema. The new database is initially empty. This command will not overwrite an existing db. schema must contain an OVSDB schema in JSON format. Refer to the OVSDB specification for details. compact db [target] Reads db and writes a compacted version. If target is specified, the compacted version is written as a new file named target, which must not already exist. If target is omitted, then the compacted version of the database replaces db in-place. convert db schema [target] Reads db, translating it into to the schema specified in schema, and writes out the new interpretation. If target is specified, the translated version is written as a new file named target, which must not already exist. If target is omitted, then the translated version of the database replaces db in-place. This command can do simple ``upgrades'' and ``downgrades'' on a database's schema. The data in db must be valid when interpreted under schema, with only one exception: data in db for tables and columns that do not exist in schema are ignored. Columns that exist in schema but not in db are set to their default values. All of schema's constraints apply in full. needs-conversion db schema Reads the schema embedded in db and the standalone schema in schema and compares them. If the schemas are the same, prints no on stdout; if they differ, print yes. db-version db schema-version schema Prints the version number in the schema embedded within the database db or in the standalone schema schema on stdout. A schema ver- sion number has the form x.y.z. See ovs-vswitchd.conf.db(5) for details. Schema version numbers and Open vSwitch version numbers are independent. If schema or db was created before schema versioning was introduced, then it will not have a version number and this command will print a blank line. db-cksum db schema-cksum schema Prints the checksum in the schema embedded within the database db or of the standalone schema schema on stdout. If schema or db was created before schema checksums were introduced, then it will not have a checksum and this command will print a blank line. query db transaction Opens db, executes transaction on it, and prints the results. The transaction must be a JSON array in the format of the params array for the JSON-RPC transact method, as described in the OVSDB specification. The db is opened for read-only access, so this command may safely run concurrently with other database activity, including ovsdb-server and other database writers. The transaction may specify database modifications, but these will have no effect on db. transact db transaction Opens db, executes transaction on it, prints the results, and commits any changes to db. The transaction must be a JSON array in the format of the params array for the JSON-RPC transact method, as described in the OVSDB specification. The db is opened and locked for read/write access, so this command will fail if the database is opened for writing by any other process, including ovsdb-server(1). Use ovsdb-client(1), instead, to write to a database that is served by ovsdb-server(1). show-log db Prints a summary of the records in db's log, including the time and date at which each database change occurred and any associated comment. This may be useful for debugging. To increase the verbosity of output, add -m (or --more) one or more times to the command line. With one -m, show-log prints a summary of the records added, deleted, or modified by each transaction. With two -ms, show-log also prints the values of the columns modified by each change to a record. OPTIONS
Logging Options -vmodule[:facility[:level]], --verbose=module[:facility[:level]] Sets the logging level for module in facility to level: o module may be any valid module name (as displayed by the --list action on ovs-appctl(8)), or the special name ANY to set the logging levels for all modules. o facility may be syslog, console, or file to set the levels for logging to the system log, the console, or a file respec- tively, or ANY to set the logging levels for both facilities. If it is omitted, facility defaults to ANY. Regardless of the log levels set for file, logging to a file will not take place unless --log-file is also specified (see below). o level must be one of off, emer, err, warn, info, or dbg, designating the minimum severity of a message for it to be logged. If it is omitted, level defaults to dbg. See ovs-appctl(8) for a definition of each log level. -v, --verbose Sets the maximum logging verbosity level, equivalent to --verbose=ANY:ANY:dbg. -vPATTERN:facility:pattern, --verbose=PATTERN:facility:pattern Sets the log pattern for facility to pattern. Refer to ovs-appctl(8) for a description of the valid syntax for pattern. --log-file[=file] Enables logging to a file. If file is specified, then it is used as the exact name for the log file. The default log file name used if file is omitted is /var/log/openvswitch/ovsdb-tool.log. Other Options -h, --help Prints a brief help message to the console. -V, --version Prints version information to the console. SEE ALSO
ovsdb-server(1), ovsdb-client(1), and the OVSDB specification. Open vSwitch November 2009 ovsdb-tool(1)
All times are GMT -4. The time now is 08:16 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy