This option opens SmartGit’s Blame window for the specified file. Smartgitc.exe -cwd C:\path -log to\repository Option “–blame” Smartgitc.exe -log C:\path\to\repository\path\to\file Example This option opens SmartGit’s Log window for the repository or file in the specified location. If the path is relative, it will be ignored. The path given with the cwd option must be an absolute path. If the open, log or blame options are specified with absolute paths, the path given with the cwd option is ignored.If the open, log or blame options are specified with relative paths, these relative paths will be resolved against the path given with the cwd option.If the open, log or blame options are specified without their own path arguments, the path given with the cwd option will be used as argument for open or log.This option sets the current working directory, which affects the path given in the open, log and blame option (see below) as follows: Smartgitc.exe -cwd C:\path -open to\repository Example Smartgitc.exe -open C:\path\to\repository Example It’s the default option and may be omitted. This option launches SmartGit and opens the repository in the specified location. On Windows, make sure to call smartgitc.exe (with ‘c’ on the end), otherwise when calling smartgit.exe this parameter has no effect, since the SmartGit process won’t be attached to any console to print the help output to. With either of the two following commands you can print all command-line options on the console that are specifically supported by the version of SmartGit you’re using: Example There may be additional options available that mainly serve debugging purposes and are therefore not documented here. Substitute it with the respective launcher for your platform if you’re not using Windows. In the following, we’ll use smartgitc.exe as an example to explain the available options. The first one is meant for regular usage, while the second one will print additional information on the console while the program runs. Windows bin\smartgit.exe or bin\smartgitc.exe.The launcher to be used depends on your platform: These options should be given as parameters to the SmartGit launcher. You may be in for the biggest check in your life.This section gives an overview of the various options SmartGit can be started with.You will get some out of space error when trying to insert data (some Oracle error message always seem to come from out of space anyway -).GROUP BY df.tablespace_name,fs.bytes,df.bytes_free,df.bytes_usedīy default, user data is the space used in the USERS tablespace.Īs for what happens when you are at the limit, I can only guess that: GROUP BY tablespace_name,bytes_free,bytes_used) df (SELECT tablespace_name,bytes_free,bytes_used Round((SUM(fs.bytes) - df.bytes_free) * 100 / fs.bytes) SELECT /* RULE */ df.tablespace_name tspace, WHERE fs.tablespace_name ( ) = df.tablespace_name Round((df.bytes - SUM(fs.bytes)) * 100 / df.bytes) "% Used" Shamelessly taken from the Oracle FAQ website, here is a query that checks used space by tablespace: SELECT /* RULE */ df.tablespace_name "Tablespace", ROUND((SPACE_USED - SPACE_RECLAIMABLE)/SPACE_LIMIT * 100, 1)Īlso, what happens when user data is above the limit? Oracle XE documentation presents a query which returns Flash Recovery Area usage, so I'm guessing there's a similar query for user data usage also. Now if I want to monitor the database to see how much user data is in use or how much memory is the database using, how would I do that? It is possible to monitor these values from Oracle Application Express, but I want to monitor the database from a centralized monitoring system. Oracle Database XE can be installed on any size host machine with any number of CPUs (one database per machine), but XE will store up to 4GB of user data, use up to 1GB of memory, and use one CPU on the host machine. As it says on the Oracle XE overview page:
0 Comments
Leave a Reply. |