recover

Recovery or Recover can refer to: read more at WikiPedia

  •  apache_maven

    In this small post I will show you how to deploy automatically some artifacts of your build into bea_logo1Weblogic 10.3 by using the weblogic-maven-plugin

    This plugin will support various tasks within the Weblogic 8.1 and 9.x environment. Such tasks as deploy, undeploy,clientgen,servicegen, and appc are supported as well as many others. The plugin uses exposed API's that are subject to change but have been tested in 8.1 SP 4-6 and 9.0 - 9.2 MP3. There are two versions of the plugin to support the two environments based on differences in the JDK. The 9.x version is currently being refactored to support the standard JSR supported deployment interface

  • joomla_cms

    mysql

    I was not seeing this error since at least 3 years:

    DB function failed with error number 1016

    Can't open file: 'jos_session.MYI' (errno: 145) SQL=INSERT INTO `jos_session`
    ( `session_id`,`time`,`username`,`gid`,`guest`,`client_id` )
    VALUES ( '4bc998b10d92bf4107976d0edacdbb26','1246725653','','0','1','0' )

    It happen sometimes and cause are unknown. While it is quite disturbing to have no more access to Joomla! frontend or backend, the fix is quite easy. You must repair this table jos_session, If you have access to


    PhpMyAdmin

    Require an access to the Plesk/CPA panel.

    Go to your Joomla database, select the table jos_session (tick the checkbox) and choose "Repair table" from the drop-down you find at the bottom of the list of tables.

    Using PHP

    Maybe the most easiest for non techies people

    I found this useful script http://www.cafewebmaster.com/repair-all-mysql-databases-tables-php, upload it at root of your host (in /httpdocs) under repair.php for example and run it, you’ll see the following:

    repair.table.in.php

    Tick repair, provide your login and password for database,

    repair.table.in.php2

    Remove the scripts after use, or add a die(‘not for use, edit script first’); at the top of it just in case it may be use to inject something in your database!

    Shell access

    For the most advanced of us, which understand Unix and have shell access

    # mysql –udblogin -p

    mysql>  use joom;

    mysql> REPAIR TABLE jos_session;
    +-------------------------+--------+----------+------------------------------------+
    | Table | Op | Msg_type | Msg_text |
    +-------------------------+--------+----------+------------------------------------+
    | joom.jos_session | repair | warning | Number of rows changed from 0 to 2 |
    | joom.jos_session | repair | status | OK |
    +-------------------------+--------+----------+------------------------------------+

    Finding Joomla! login and password

    These informations can be found in httpdocs/configuration.php under $user and $password as seen below

    ..

    var $user = 'hkuin47Gdfver';
    var $db = 'joom';
    var $dbprefix = 'dfrtCsdef_';
    var $mailer = 'mail';
    var $fromname = 'Happpp';
    var $sendmail = '/usr/sbin/sendmail';
    var $smtpauth = '0';
    var $smtpsecure = 'none';
    var $smtpport = '25';
    var $smtpuser = '';
    var $smtppass = '';
    var $smtphost = 'localhost';
    var $MetaAuthor = '1';
    var $MetaTitle = '1';
    var $lifetime = '15';
    var $session_handler = 'database';
    var $password = afedfhrr546fdhcfcv;

    ..

    And if the repair failed?

    Run the following sql to drop the table and make it new. Copy it into the PhpMyAdmin SQL field.

    DROP table if exist `jos_session`

    CREATE TABLE `jos_session` (
      `username` varchar(150) default '',
      `time` varchar(14) default '',
      `session_id` varchar(200) NOT NULL default '0',
      `guest` tinyint(4) default '1',
      `userid` int(11) default '0',
      `usertype` varchar(50) default '',
      `gid` tinyint(3) unsigned NOT NULL default '0',
      `client_id` tinyint(3) unsigned NOT NULL default '0',
      `data` longtext,
      PRIMARY KEY  (`session_id`(64)),
      KEY `whosonline` (`guest`,`usertype`),
      KEY `userid` (`userid`),
      KEY `time` (`time`)
    ) TYPE=MyISAM CHARACTER SET `utf8`;

  • The Oracle error ORA-00054 can be solved by executing as DBA the following query

    select p.spid,s.sid,s.serial#,s.username,s.status,s.last_call_et,
           p.program,p.terminal,logon_time,module,s.osuser 
    from 
           V$process p,V$session s 
    where 
           s.paddr = p.addr and s.status = &39;ACTIVE&39; and 
           s.username not like &39;%SYS%&39;;

    This will return the PID of the hanging process

    You can then SSH to the server ruining oracle and kill the process

    kill -9 PID