Internet in OpenSolaris and VirtualBox combo

Installed VirtualBox 2.0.0 on my Windows Vista SP1 machine, then booted on a live CD image of OpenSolaris inside VirtualBox. In the live CD, OpenSolaris was able to connect to the internet. But after installing it on the virtual hard drive, it showed no internet connection.
After googling, I restarted the virtual machine and now I am making this entry inside OpenSolaris/VirtualBox. Cool!

Plans not displaying in Customer Center: Issue 2

Even though most of the accounts reported in Issue 1 were resolved, there were still some accounts that has the same problem. The reasons are varied. The following were some of the reasons that is causing the issue:

• Missing plans - this is caused by somebody deleting deals/plans in the database a while back. Even though most of the plans were recreated in the database, a few plans were not. The error it logs in the DM is: NOTICE OP_ROBJ: do_sql_select() NOTHING FOUND ("/plan", XXXXXXX) where XXXXXXX is the plan poid.
  

• Missing deals - same reason as above. For the missing plan/deal issue, the workaround was to create the mentioned plan/deal in by inserting a record in the database. This path was chosen because there was already a precedent to this issue i.e. somebody deleted the deals/plans in production and operations decided to just create them manually in the database since they are not offered to customers anymore.
  

• DM logs say Portal is looking for a plan with POID 0 for a particular account. This one is different from the others. It was confusing considering the object /plan 0 shouldn't have existed in the first place. After checking the logs, it appears that BRM looks at the event_billing_product_action table for the deals/plans when you want to display the plans in CC. Apparently, if the service is still active, BRM will look for the plan object that is in the flist returned by the query to the product action event table. If not active, it will not look for the plan object. For unknown reasons, this account has '/plan 0' in the product action event table and has a valid deal. Since the service associated with the deal/product is still active, BRM attempts to look for this '/plan 0' in the plan table and throws the error when it cannot find it. The two options were either to insert a '/plan 0' in the database or update the event table to reflect the correct plan for the account. By looking at the deal object in the event table, one can deduce the plan to which it belongs. The second option was chosen to be implemented in production.